Mercurial > hg > xemacs-beta

comparison man/xemacs/keystrokes.texi @ 412:697ef44129c6 r21-2-14

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Import from CVS: tag r21-2-14
author cvs
date Mon, 13 Aug 2007 11:20:41 +0200
parents de805c49cfc1
children
comparison
equal deleted inserted replaced
411:12e008d41344 412:697ef44129c6
141 Pressing the @key{BREAK} key. 141 Pressing the @key{BREAK} key.
142 @item (control meta button2up) 142 @item (control meta button2up)
143 Release the middle mouse button, while pressing @key{CTRL} and 143 Release the middle mouse button, while pressing @key{CTRL} and
144 @key{META}. 144 @key{META}.
145 @end table 145 @end table
146 @cindex shift modifier 146 @cindex shift modifer
147 Note: As you define keystrokes, you can use the @kbd{shift} key only 147 Note: As you define keystrokes, you can use the @kbd{shift} key only
148 as a modifier with characters that do not have a second keysym on the 148 as a modifier with characters that do not have a second keysym on the
149 same key, such as @kbd{backspace} and @kbd{tab}. It is an error to 149 same key, such as @kbd{backspace} and @kbd{tab}. It is an error to
150 define a keystroke using the @key{shift} modifier with keysyms such as 150 define a keystroke using the @key{shift} modifier with keysyms such as
151 @kbd{a} and @kbd{=}. The correct forms are @kbd{A} and @kbd{+}. 151 @kbd{a} and @kbd{=}. The correct forms are @kbd{A} and @kbd{+}.
161 161
162 Emacs represents a key sequence as a vector of keystrokes. Thus, the 162 Emacs represents a key sequence as a vector of keystrokes. Thus, the
163 schematic representation of a complete key sequence is as follows: 163 schematic representation of a complete key sequence is as follows:
164 164
165 @example 165 @example
166 [(modifier .. modifier keysym) ... (modifier .. modifier keysym)] 166 [(modifier .. modifer keysym) ... (modifier .. modifier keysym)]
167 @end example 167 @end example
168 168
169 Here are some examples of complete key sequences: 169 Here are some examples of complete key sequences:
170 170
171 @table @kbd 171 @table @kbd
172 @item [(control c) (control a)] 172 @item [(control c) (control a)]
173 Typing @kbd{C-c} followed by @kbd{C-a} 173 Typing @kbd{C-c} followed by @kbd{C-a}
174 @item [(control c) (control 65)] 174 @item [(control c) (control 65)]
175 Typing @kbd{C-c} followed by @kbd{C-a}. (Using the ASCII code 175 Typing @kbd{C-c} followed by @kbd{C-a}. (Using the ASCII code
176 for the character `a')@refill 176 for the character `a')@refill
177 @item [(control c) (break)] 177 @item [(control c) (break)]
178 Typing @kbd{C-c} followed by the @kbd{break} character.@refill 178 Typing @kbd{C-c} followed by the @kbd{break} character.@refill
179 @end table 179 @end table
297 do the following: 297 do the following:
298 298
299 Create a file called @code{~/.xmodmap}. In this file, place the lines 299 Create a file called @code{~/.xmodmap}. In this file, place the lines
300 300
301 @example 301 @example
302 remove Lock = Caps_Lock 302 remove Lock = Caps_Lock
303 keysym Caps_Lock = Super_L 303 keysym Caps_Lock = Super_L
304 add Mod2 = Super_L 304 add Mod2 = Super_L
305 @end example 305 @end example
306 306
307 The first line says that the key that is currently called @code{Caps_Lock} 307 The first line says that the key that is currently called @code{Caps_Lock}
308 should no longer behave as a ``lock'' key. The second line says that 308 should no longer behave as a ``lock'' key. The second line says that
309 this should now be called @code{Super_L} instead. The third line says that 309 this should now be called @code{Super_L} instead. The third line says that