comparison lispref/commands.texi @ 27301:8c79b30d8475

*** empty log message ***
author Richard M. Stallman <rms@gnu.org>
date Wed, 12 Jan 2000 05:22:30 +0000
parents 89afca54a135
children 13029a808e20
comparison
equal deleted inserted replaced
27300:baffb2de5ce9 27301:8c79b30d8475
1867 line or a scroll bar, the event type shows nothing special---it is the 1867 line or a scroll bar, the event type shows nothing special---it is the
1868 same symbol that would normally represent that combination of mouse 1868 same symbol that would normally represent that combination of mouse
1869 button and modifier keys. The information about the window part is kept 1869 button and modifier keys. The information about the window part is kept
1870 elsewhere in the event---in the coordinates. But 1870 elsewhere in the event---in the coordinates. But
1871 @code{read-key-sequence} translates this information into imaginary 1871 @code{read-key-sequence} translates this information into imaginary
1872 ``prefix keys'', all of which are symbols: @code{heder-line}, 1872 ``prefix keys'', all of which are symbols: @code{header-line},
1873 @code{horizontal-scroll-bar}, @code{menu-bar}, @code{mode-line}, 1873 @code{horizontal-scroll-bar}, @code{menu-bar}, @code{mode-line},
1874 @code{vertical-line}, and @code{vertical-scroll-bar}. You can define 1874 @code{vertical-line}, and @code{vertical-scroll-bar}. You can define
1875 meanings for mouse clicks in special window parts by defining key 1875 meanings for mouse clicks in special window parts by defining key
1876 sequences using these imaginary prefix keys. 1876 sequences using these imaginary prefix keys.
1877 1877