[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Non-character input events
From: |
Kevin Rodgers |
Subject: |
Re: Non-character input events |
Date: |
Mon, 24 Mar 2003 09:48:07 -0700 |
User-agent: |
Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:0.9.4.1) Gecko/20020406 Netscape6/6.2.2 |
Joe Fineman wrote:
Which Elisp manual is that? I have downloaded both the version 21.2
manual and the version 20.3 manual from the Gnu Web site, and each
contains only one bare mention of input events.
Even the venerable 19.34 elisp manual contains this:
File: elisp, Node: Input Events, Next: Reading Input, Prev: Command Loop
Info, Up: Command Loop
Input Events
============
The Emacs command loop reads a sequence of "input events" that
represent keyboard or mouse activity. The events for keyboard activity
are characters or symbols; mouse events are always lists. This section
describes the representation and meaning of input events in detail.
- Function: eventp OBJECT
This function returns non-`nil' if OBJECT is an input event.
* Menu:
* Keyboard Events:: Ordinary characters-keys with symbols on them.
* Function Keys:: Function keys-keys with names, not symbols.
* Mouse Events:: Overview of mouse events.
* Click Events:: Pushing and releasing a mouse button.
* Drag Events:: Moving the mouse before releasing the button.
* Button-Down Events:: A button was pushed and not yet released.
* Repeat Events:: Double and triple click (or drag, or down).
* Motion Events:: Just moving the mouse, not pushing a button.
* Focus Events:: Moving the mouse between frames.
* Misc Events:: Other events window systems can generate.
* Event Examples:: Examples of the lists for mouse events.
* Classifying Events:: Finding the modifier keys in an event symbol.
Event types.
* Accessing Events:: Functions to extract info from events.
* Strings of Events:: Special considerations for putting
keyboard character events in a string.
--
<a href="mailto:<kevin.rodgers@ihs.com>">Kevin Rodgers</a>