mirror/emacs
1
0
Fork 0
mirror of https://git.savannah.gnu.org/git/emacs.git synced 2024-11-24 07:20:37 +00:00
Code Issues Releases Activity

; Minor copyedits in manuals.

Browse Source 
* doc/lispref/variables.texi (Lexical Binding): The future is here.

* doc/emacs/files.texi (Copying and Naming): Use @w{..} around
constructs that could be split between lines, but shouldn't.
This commit is contained in:
Eli Zaretskii 2017-08-18 09:33:11 +03:00
parent 7ab95461f7
commit bc5fba7aae
2 changed files with 11 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/emacs/files.texi
View File

@ -1556,10 +1556,14 @@ not accept wildcard file names.
In all these commands, if the argument @var{new} is just a directory
name, the real new name is in that directory, with the same
non-directory component as @var{old}. For example,
non-directory component as @var{old}. For example, the command
@c FIXME: '/tmp' should be '/tmp/' because '/tmp'
@c is not "just a directory name".
@kbd{M-x rename-file @key{RET} ~/foo @key{RET} /tmp @key{RET}}
@c And actually the fact that ``directory name'' must end in a slash
@c is not explained anywhere in this manual. Moreover, it many times
@c uses ``directory name'' in contexts where the string it alludes to
@c will clearly _not_ end in a slash
@w{@kbd{M-x rename-file @key{RET} ~/foo @key{RET} /tmp @key{RET}}}
renames @file{~/foo} to @file{/tmp/foo}. All these
commands ask for confirmation when the new file name already exists,
too.
@ -1586,8 +1590,8 @@ different file systems, the file @var{old} is copied and deleted.
@ifnottex
If a file is under version control (@pxref{Version Control}), you
should rename it using @kbd{M-x vc-rename-file} instead of @kbd{M-x
rename-file}. @xref{VC Delete/Rename}.
should rename it using @w{@kbd{M-x vc-rename-file}} instead of
@w{@kbd{M-x rename-file}}. @xref{VC Delete/Rename}.
@end ifnottex
@findex add-name-to-file

6
doc/lispref/variables.texi
View File

@ -1017,11 +1017,11 @@ variables like @code{case-fold-search}:
@subsection Lexical Binding
Lexical binding was introduced to Emacs, as an optional feature, in
version 24.1. We expect its importance to increase in the future.
version 24.1. We expect its importance to increase with time.
Lexical binding opens up many more opportunities for optimization, so
programs using it are likely to run faster in future Emacs versions.
Lexical binding is also more compatible with concurrency, which we
want to add to Emacs in the future.
Lexical binding is also more compatible with concurrency, which was
added to Emacs in version 26.1.
A lexically-bound variable has @dfn{lexical scope}, meaning that any
reference to the variable must be located textually within the binding