Mercurial > emacs
changeset 12125:995be67f3fd1
updates for version 19.29.
,
| author | Melissa Weisshaus <melissa@gnu.org> |
|---|---|
| date | Thu, 08 Jun 1995 04:43:19 +0000 |
| parents | 437eb190e7a7 |
| children | 0b0b0c2e5254 |
| files | lispref/frames.texi lispref/keymaps.texi lispref/processes.texi lispref/searching.texi lispref/windows.texi |
| diffstat | 5 files changed, 6 insertions(+), 6 deletions(-) [+] |
line wrap: on
line diff
--- a/lispref/frames.texi Thu Jun 08 04:16:18 1995 +0000 +++ b/lispref/frames.texi Thu Jun 08 04:43:19 1995 +0000 @@ -15,7 +15,7 @@ @cindex terminal frame @cindex X window frame When Emacs runs on a text-only terminal, it starts with one -@dfn{terminal frames}. If you create additional ones, Emacs displays +@dfn{terminal frame}. If you create additional ones, Emacs displays one and only one at any given time---on the terminal screen, of course. When Emacs communicates directly with an X server, it does not have a @@ -581,7 +581,7 @@ @end defun Some window managers provide a command to delete a window. These work -by sending a special message to the program than operates the window. +by sending a special message to the program that operates the window. When Emacs gets one of these commands, it generates a @code{delete-frame} event, whose normal definition is a command that calls the function @code{delete-frame}. @xref{Misc Events}.
--- a/lispref/keymaps.texi Thu Jun 08 04:16:18 1995 +0000 +++ b/lispref/keymaps.texi Thu Jun 08 04:43:19 1995 +0000 @@ -1488,7 +1488,7 @@ If an alias command has no keyboard equivalent itself, menus show the keyboard equivalent of its underlying command. In the example above, -menus items defined to run @code{make-read-only} or @code{make-writable} +menu items defined to run @code{make-read-only} or @code{make-writable} would show the keyboard equivalents of @code{toggle-read-only}. @node Mouse Menus
--- a/lispref/processes.texi Thu Jun 08 04:16:18 1995 +0000 +++ b/lispref/processes.texi Thu Jun 08 04:43:19 1995 +0000 @@ -887,7 +887,7 @@ If an error happens during execution of a filter function, it is caught automatically, so that it doesn't stop the execution of whatever -programs was running when the filter function was started. However, if +program was running when the filter function was started. However, if @code{debug-on-error} is non-@code{nil}, the error-catching is turned off. This makes it possible to use the Lisp debugger to debug the filter function. @xref{Debugger}.
--- a/lispref/searching.texi Thu Jun 08 04:16:18 1995 +0000 +++ b/lispref/searching.texi Thu Jun 08 04:43:19 1995 +0000 @@ -991,7 +991,7 @@ last regular expression searched for, or a subexpression of it. If @var{count} is zero, then the value is the position of the start of -the entire match. Otherwise, @var{count}, specifies a subexpression in +the entire match. Otherwise, @var{count} specifies a subexpression in the regular expresion, and the value of the function is the starting position of the match for that subexpression.
--- a/lispref/windows.texi Thu Jun 08 04:16:18 1995 +0000 +++ b/lispref/windows.texi Thu Jun 08 04:43:19 1995 +0000 @@ -286,7 +286,7 @@ This function returns non-@code{nil} if there is only one window. The argument @var{no-mini}, if non-@code{nil}, means don't count the minibuffer even if it is active; otherwise, the minibuffer window is -included, if active, in the total number of windows, which is compared +included, if active, in the total number of windows, which is compared against one. The argument @var{all-frames} specifies which frames to consider. Here