diff options
author | Eli Zaretskii <eliz@gnu.org> | 2018-04-13 16:44:05 +0300 |
---|---|---|
committer | Eli Zaretskii <eliz@gnu.org> | 2018-04-13 16:44:05 +0300 |
commit | 6bdcaec885fb1272617e7e02c6d1e571163b15f5 (patch) | |
tree | a510888934c29465e43d744083cabea5e51cf841 /doc/lispref/variables.texi | |
parent | febac2796b01b120476c9c38bfe1b32fb4f56f23 (diff) | |
download | emacs-6bdcaec885fb1272617e7e02c6d1e571163b15f5.tar.gz emacs-6bdcaec885fb1272617e7e02c6d1e571163b15f5.tar.bz2 emacs-6bdcaec885fb1272617e7e02c6d1e571163b15f5.zip |
Fix typos and minor wording issues in ELisp manual
* doc/lispref/internals.texi (Writing Emacs Primitives):
* doc/lispref/display.texi (Temporary Displays): Fix typos.
* doc/lispref/text.texi (Filling, Changing Properties)
(Transposition): Clarify and fix typos.
* doc/lispref/positions.texi (Screen Lines): Improve wording.
* doc/lispref/modes.texi (Minor Mode Conventions)
(Font Lock Multiline): Fix typos.
* doc/lispref/variables.texi (Dynamic Binding Tips): Fix a
cross-reference. Fix a typo.
* doc/lispref/sequences.texi (Sequence Functions): Fix typos.
(Bug#31143)
Diffstat (limited to 'doc/lispref/variables.texi')
-rw-r--r-- | doc/lispref/variables.texi | 15 |
1 files changed, 8 insertions, 7 deletions
diff --git a/doc/lispref/variables.texi b/doc/lispref/variables.texi index 4d04335d83a..af1bed461c0 100644 --- a/doc/lispref/variables.texi +++ b/doc/lispref/variables.texi @@ -1004,12 +1004,13 @@ affect, nor be affected by, any uses of the same variable symbol elsewhere in the program. @item -Otherwise, define the variable with @code{defvar}, @code{defconst}, or -@code{defcustom}. @xref{Defining Variables}. Usually, the definition -should be at top-level in an Emacs Lisp file. As far as possible, it -should include a documentation string which explains the meaning and -purpose of the variable. You should also choose the variable's name -to avoid name conflicts (@pxref{Coding Conventions}). +Otherwise, define the variable with @code{defvar}, @code{defconst} +(@pxref{Defining Variables}), or @code{defcustom} (@pxref{Variable +Definitions}). Usually, the definition should be at top-level in an +Emacs Lisp file. As far as possible, it should include a +documentation string which explains the meaning and purpose of the +variable. You should also choose the variable's name to avoid name +conflicts (@pxref{Coding Conventions}). Then you can bind the variable anywhere in a program, knowing reliably what the effect will be. Wherever you encounter the variable, it will @@ -1024,7 +1025,7 @@ variables like @code{case-fold-search}: @group (defun search-for-abc () "Search for the string \"abc\", ignoring case differences." - (let ((case-fold-search nil)) + (let ((case-fold-search t)) (re-search-forward "abc"))) @end group @end example |