diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/emacs/dired.texi | 28 | ||||
| -rw-r--r-- | doc/emacs/display.texi | 2 | ||||
| -rw-r--r-- | doc/lispref/nonascii.texi | 2 | ||||
| -rw-r--r-- | doc/lispref/objects.texi | 15 | ||||
| -rw-r--r-- | doc/misc/efaq.texi | 5 |
5 files changed, 37 insertions, 15 deletions
diff --git a/doc/emacs/dired.texi b/doc/emacs/dired.texi index fbb3030c2a4..007a943714a 100644 --- a/doc/emacs/dired.texi +++ b/doc/emacs/dired.texi @@ -238,19 +238,21 @@ the buffer, and no files actually deleted. @cindex recursive deletion @vindex dired-recursive-deletes You can delete empty directories just like other files, but normally -Dired cannot delete directories that are nonempty. If the variable -@code{dired-recursive-deletes} is non-@code{nil}, then Dired can -delete nonempty directories including all their contents. That can be -somewhat risky. If the value of the variable is @code{always}, Dired -will delete nonempty directories recursively, which is even more -risky. Even if you have set @code{dired-recursive-deletes} to -@code{nil}, you might want sometimes to delete recursively directories -without being asked for confirmation for all of them. This is handy -when you have marked many directories for deletion and you are very -sure that all of them can safely be deleted. For every nonempty -directory you are asked for confirmation; if you answer @code{all}, -then all the remaining directories will be deleted without more -questions. +Dired cannot delete directories that are nonempty. However, if the +variable @code{dired-recursive-deletes} is non-@code{nil}, then Dired +is allowed to delete nonempty directories including all their +contents. That can be somewhat risky. If the value of the variable +is @code{always}, Dired will delete nonempty directories recursively, +which is even more risky. + +Even if you have set @code{dired-recursive-deletes} to @code{nil}, you +might want sometimes to delete directories recursively without being +asked for confirmation for all of them. For example, you may want +that when you have marked many directories for deletion and you are +very sure that all of them can safely be deleted. For every nonempty +directory you are asked for confirmation to delete, if you answer +@code{all}, then all the remaining directories will be deleted without +any further questions. @vindex delete-by-moving-to-trash@r{, and Dired} If you change the variable @code{delete-by-moving-to-trash} to diff --git a/doc/emacs/display.texi b/doc/emacs/display.texi index c60cf649146..2f5ce80d607 100644 --- a/doc/emacs/display.texi +++ b/doc/emacs/display.texi @@ -1253,7 +1253,7 @@ customize the variable @code{whitespace-line-column}. Highlight newlines. @item empty -Highlight empty lines. +Highlight empty lines at the beginning and/or end of the buffer. @item big-indent @vindex whitespace-big-indent-regexp diff --git a/doc/lispref/nonascii.texi b/doc/lispref/nonascii.texi index 70df555d877..4d75d6a1f14 100644 --- a/doc/lispref/nonascii.texi +++ b/doc/lispref/nonascii.texi @@ -460,7 +460,7 @@ of character properties. In particular, Emacs supports the @uref{http://www.unicode.org/reports/tr23/, Unicode Character Property Model}, and the Emacs character property database is derived from the Unicode Character Database (@acronym{UCD}). See the -@uref{http://www.unicode.org/versions/Unicode6.2.0/ch04.pdf, Character +@uref{http://www.unicode.org/versions/latest/ch04.pdf, Character Properties chapter of the Unicode Standard}, for a detailed description of Unicode character properties and their meaning. This section assumes you are already familiar with that chapter of the diff --git a/doc/lispref/objects.texi b/doc/lispref/objects.texi index 78a7dccc88d..1253e46297f 100644 --- a/doc/lispref/objects.texi +++ b/doc/lispref/objects.texi @@ -2154,6 +2154,21 @@ Symbols}. @result{} nil @end group @end example + +@noindent +@cindex identical-contents objects, and byte-compiler +@cindex objects with identical contents, and byte-compiler +The Emacs Lisp byte compiler may collapse identical literal objects, +such as literal strings, into references to the same object, with the +effect that the byte-compiled code will compare such objects as +@code{eq}, while the interpreted version of the same code will not. +Therefore, your code should never rely on objects with the same +literal contents being either @code{eq} or not @code{eq}, it should +instead use functions that compare object contents such as +@code{equal}, described below. Similarly, your code should not modify +literal objects (e.g., put text properties on literal strings), since +doing that might affect other literal objects of the same contents, if +the byte compiler collapses them. @end defun @defun equal object1 object2 diff --git a/doc/misc/efaq.texi b/doc/misc/efaq.texi index 862d2831804..903c56cef90 100644 --- a/doc/misc/efaq.texi +++ b/doc/misc/efaq.texi @@ -1068,6 +1068,11 @@ which opens a vulnerability for Emacs users receiving Enriched Text from external sources. Execution of arbitrary Lisp forms in @code{display} properties decoded by Enriched Text mode is now disabled by default. + +@cindex Unicode 11.0.0 +@item +Emacs 26.2 comes with data files imported from the latest Unicode +Standard version 11.0.0. @end itemize Consult the Emacs @file{NEWS} file (@kbd{C-h n}) for the full list of |