Mercurial > emacs
changeset 76835:e5b96737f906
Improve indexing.
author | Eli Zaretskii <eliz@gnu.org> |
---|---|
date | Sat, 31 Mar 2007 13:56:30 +0000 |
parents | 8a72a36a4779 |
children | 9feeb7a817c0 |
files | lispref/commands.texi lispref/display.texi lispref/frames.texi lispref/minibuf.texi lispref/nonascii.texi lispref/os.texi lispref/processes.texi lispref/windows.texi |
diffstat | 8 files changed, 14 insertions(+), 0 deletions(-) [+] |
line wrap: on
line diff
--- a/lispref/commands.texi Sat Mar 31 13:44:56 2007 +0000 +++ b/lispref/commands.texi Sat Mar 31 13:56:30 2007 +0000 @@ -933,6 +933,7 @@ @node Keyboard Events @subsection Keyboard Events +@cindex keyboard events There are two kinds of input you can get from the keyboard: ordinary keys, and function keys. Ordinary keys correspond to characters; the @@ -2077,6 +2078,8 @@ @node Reading Input @section Reading Input +@cindex read input +@cindex keyboard input The editor command loop reads key sequences using the function @code{read-key-sequence}, which uses @code{read-event}. These and other
--- a/lispref/display.texi Sat Mar 31 13:44:56 2007 +0000 +++ b/lispref/display.texi Sat Mar 31 13:56:30 2007 +0000 @@ -4270,6 +4270,7 @@ @node Image Cache @subsection Image Cache +@cindex image cache Emacs stores images in an image cache when it displays them, so it can display them again more efficiently. It removes an image from the cache
--- a/lispref/frames.texi Sat Mar 31 13:44:56 2007 +0000 +++ b/lispref/frames.texi Sat Mar 31 13:56:30 2007 +0000 @@ -193,6 +193,7 @@ @node Frame Parameters @section Frame Parameters +@cindex frame parameters A frame has many parameters that control its appearance and behavior. Just what parameters a frame has depends on what display mechanism it
--- a/lispref/minibuf.texi Sat Mar 31 13:44:56 2007 +0000 +++ b/lispref/minibuf.texi Sat Mar 31 13:56:30 2007 +0000 @@ -1222,6 +1222,8 @@ @node Reading File Names @subsection Reading File Names +@cindex read file names +@cindex prompt for file name Here is another high-level completion function, designed for reading a file name. It provides special features including automatic insertion
--- a/lispref/nonascii.texi Sat Mar 31 13:44:56 2007 +0000 +++ b/lispref/nonascii.texi Sat Mar 31 13:56:30 2007 +0000 @@ -408,6 +408,7 @@ @node Splitting Characters @section Splitting Characters +@cindex split character The functions in this section convert between characters and the byte values used to represent them. For most purposes, there is no need to @@ -433,6 +434,7 @@ @end example @end defun +@cindex generate characters in charsets @defun make-char charset &optional code1 code2 This function returns the character in character set @var{charset} whose position codes are @var{code1} and @var{code2}. This is roughly the
--- a/lispref/os.texi Sat Mar 31 13:44:56 2007 +0000 +++ b/lispref/os.texi Sat Mar 31 13:56:30 2007 +0000 @@ -1697,6 +1697,7 @@ @node Recording Input @subsection Recording Input +@cindex recording input @defun recent-keys This function returns a vector containing the last 300 input events from
--- a/lispref/processes.texi Sat Mar 31 13:44:56 2007 +0000 +++ b/lispref/processes.texi Sat Mar 31 13:56:30 2007 +0000 @@ -1236,6 +1236,7 @@ @node Decoding Output @subsection Decoding Process Output +@cindex decode process output When Emacs writes process output directly into a multibyte buffer, it decodes the output according to the process output coding system. @@ -1285,6 +1286,7 @@ @node Accepting Output @subsection Accepting Output from Processes +@cindex accept input from processes Output from asynchronous subprocesses normally arrives only while Emacs is waiting for some sort of external event, such as elapsed time @@ -1643,6 +1645,7 @@ @node Network Servers @section Network Servers +@cindex network servers You create a server by calling @code{make-network-process} with @code{:server t}. The server will listen for connection requests from
--- a/lispref/windows.texi Sat Mar 31 13:44:56 2007 +0000 +++ b/lispref/windows.texi Sat Mar 31 13:56:30 2007 +0000 @@ -1195,6 +1195,7 @@ @noindent @xref{Positions}, for more details on buffer positions. +@cindex cursor As far as the user is concerned, point is where the cursor is, and when the user switches to another buffer, the cursor jumps to the position of point in that buffer.