Merge from origin/emacs-26

0276743 (origin/emacs-26) Doc string fix in latin-alt.el
c9269af Minor improvements in package.texi
898a3e4 Minor improvement in Emacs user manual
8f7d718 * doc/lispref/anti.texi (Antinews): Replace 25.2 with 25.3.
989d0af Improve documentation of mini-window resizing
923e415 More changes in the Emacs manual
565adf2 Clarify that text-quoting-style doesn't affect *Info* (Bug#24...
2dd273b Mention that shell quoting of % on w32 may fail (Bug#19350)
19fa6d5 Fix --no-build-details for w32 and macOS
979944c * doc/lispref/anti.texi (Antinews): Add some more antinews.
c2727e3 Fix crashes when run with --no-build-details
dc08490 More changes for the manual
04c5bd5 Doc fixes for process functions (Bug#30349)
e209034 Fix shr and CSS 4 color maps
5fe8192 Yet another round of improvements in the manual

Conflicts:
	doc/emacs/files.texi
	test/lisp/subr-tests.el

6 files changed, 206 insertions, 20 deletions

diff --git a/doc/lispref/anti.texi b/doc/lispref/anti.texi
index b6df9fe2e39..ef28415d591 100644
--- a/doc/lispref/anti.texi
+++ b/doc/lispref/anti.texi
@@ -10,7 +10,7 @@
 @c Update the elisp.texi Antinews menu entry with the above version number.
 
 For those users who live backwards in time, here is information about
-downgrading to Emacs version 25.2.  We hope you will enjoy the greater
+downgrading to Emacs version 25.3.  We hope you will enjoy the greater
 simplicity that results from the absence of many @w{Emacs
 @value{EMACSVER}} features.
 
@@ -48,6 +48,15 @@ specialized library for their support was deemed an unnecessary
 maintenance burden.
 
 @item
+The time conversion functions @code{current-time-string},
+@code{current-time-zone}, @code{decode-time},
+@code{format-time-string}, and @code{set-time-zone-rule} no longer
+accept integer offsets as time zone rules, to make it more of a
+challenge to convert foreign timestamps.  Also,
+@code{format-time-string} no longer converts @samp{%q} to the calendar
+quarter, as that is something you can easily do for yourself.
+
+@item
 Field numbers like @samp{%2$} in format specifiers are no longer
 available.  We decided that their use makes code reading and
 comprehension much harder, and that having them is unjustified in the
@@ -84,12 +93,38 @@ confusing differences between the operation of these functions in
 interactive and non-interactive invocations has been removed.
 
 @item
+Several functions that create or rename their files now treat their
+destination specially if it happens to be a directory, even when its
+name does not appear to be that of a directory.  For example,
+@code{(rename-file "A" "B")} no longer renames @file{A} to @file{B} if
+@file{B} happens to be a directory.  This is so that dealing with
+files becomes more of an adventure.
+
+@item
+The @code{format} function now returns new strings in more cases, to
+place more stress on the Emacs memory manager and thereby test Emacs
+better.
+
+@item
 The function @file{assoc} has been simplified by removing its third
 optional argument.  It now always uses @code{equal} for comparison.
 Likewise, @code{alist-get} always uses @code{assq}, and @code{map-get}
 and @code{map-put} always use @code{eql} for their comparisons.
 
 @item
+Numeric comparisons and the functions @code{format},
+@code{make-hash-table}, @code{min}, @code{max} and @code{logb} now
+occasionally round values internally to make their results less
+predictable.
+
+@item
+The functions @code{ffloor}, @code{fceiling}l, @code{ftruncate} and
+@code{fround} now accept integer arguments.  Conversely, functions
+like @code{decode-char} that accept floating-point integers now accept
+arguments that are not integers.  In both cases the results are
+amusingly nonsensical sometimes.
+
+@item
 GnuTLS cryptographic functions are no longer available in Emacs.  We
 have decided that the needs for such functionality are deteriorating,
 and their cumbersome interfaces make them hard to use.
@@ -104,16 +139,25 @@ broken by records.
 You can again use @code{string-as-unibyte},
 @code{string-make-multibyte}, and other similar functions, without
 being annoyed by messages about their deprecation.  This is in
-preparation for removal of multibyte text from Emacs in the distance
+preparation for removal of multibyte text from Emacs in the distant
 past.
 
 @item
+The @code{string-version-lessp} function has been removed, to
+encourage programmers to use their own idiosyncratic methods to
+determine whether one version string precedes another.
+
+@item
 The function @code{read-color} no longer displays color names using
 each color as the background.  We have determined that this surprises
 users and produces funny inconsistent results on color-challenged
 terminals.
 
 @item
+Support for 24-bit color on text terminals has been dropped, since
+it wasn't needed long ago.
+
+@item
 We removed the function @code{file-name-case-insensitive-p}, as
 testing for the OS symbol should be enough for the observable past to
 come, and learning to use yet another API is a burden.
@@ -136,12 +180,57 @@ The function @code{mapcan} is gone; use @code{mapcar} instead, and
 process the resulting list as you see fit.
 
 @item
+Low-level list functions like @code{length} and @code{member} can now
+loop indefinitely when given cyclic lists, causing Emacs to freeze.
+This can help these functions run a tiny bit faster in the usual case
+where the input is not cyclic.
+
+@item
+The @code{write-region} function no longer propagates its
+@var{lockname} argument to file name handlers.
+
+@item
 You can once again write a Lisp program that returns funny random
 values from @code{file-attributes} by having another process alter the
 filesystem while Emacs is accessing the file.  This can give rise to
 some interesting applications in the near past.
 
 @item
+The functions @code{file-attributes}, @code{file-symlink-p}, and
+@code{make-symbolic-link} now quietly mutate the target of a local
+symbolic link in some cases, to make it more of a challenge to deal
+with arbitrary symlinks in Emacs code.
+
+@item
+The error @code{file-missing} has been removed; operations now lump
+such errors into the @code{file-error} category instead.
+
+@item
+The function @code{delete-directory} now signals an error if operating
+recursively and some other process deletes the directory before this
+function gets to it.
+
+@item
+The @code{dutch} input method now attempts to support Turkish too,
+albeit incorrectly.  Also, it converts @samp{IJ} and @samp{ij} to
+special characters instead of leaving them alone.
+
+@item
+Non-breaking hyphens and approximations to quotes are now displayed
+just with the @code{escape-glyph} face instead of having faces of
+their own.  This is simpler and gives the user amusing puzzles to
+solve when viewing text containing these characters.
+
+@item
+The user option @code{electric-quote-context-sensitive} and the
+variable @code{electric-quote-inhibit-functions}, so that electric
+quoting is simpler and more likely to do the wrong thing.
+
+@item
+The user option @code{text-quoting-style} has been removed, and is now
+just a variable.
+
+@item
 We have removed the functions @code{file-name-quote},
 @code{file-name-unquote}, and @code{file-name-quoted-p}.  Writing code
 that checks whether a file name is already quoted is easy, and doubly
@@ -160,6 +249,34 @@ customizable only based on buffers; the @code{mode-line-format} and
 @code{header-line-format} window parameters have been removed.
 
 @item
+Emacs now normally builds a limited @command{movemail} substitute that
+retrieves POP3 email only via insecure channels, and the
+configure-time option @option{--with-mailutils} has been removed.
+This simplifies Emacs setup when security is not important.
+
+@item
+The configure-time option @option{--enable-gcc-warnings=warn-only}
+has been removed, so that build-time warnings are always fatal now.
+
+@item
+The configure-time option @option{--disable-build-details} has been
+removed.  This way, Emacs builds are unique and irreproducible.
+
+@item
+The variable @code{emacs-version} now includes the build number
+instead of storing it separately in @code{emacs-build-number}.
+
+@item
+Emacs has been ported to IRIX.
+
+@item
+Several options and variables have been removed to simplify Emacs and
+potentially make it less reliable.  These include the
+@option{--module-assertions} option, the
+@code{attempt-stack-overflow-recovery} variable, and the
+@code{attempt-orderly-shutdown-on-fatal-signal} variable.
+
+@item
 As part of the ongoing quest for simplicity, many other functions and
 variables have been eliminated.
 @end itemize
diff --git a/doc/lispref/backups.texi b/doc/lispref/backups.texi
index 8ca10d7905c..8ce8f6180d1 100644
--- a/doc/lispref/backups.texi
+++ b/doc/lispref/backups.texi
@@ -775,16 +775,80 @@ after inserting the modified contents.  A custom @code{revert-buffer-function}
 may or may not run this hook.
 @end defvar
 
-@c FIXME?  Move this section from arevert-xtra to here?
+Emacs can revert buffers automatically.  It does that by default for
+buffers visiting files.  The following describes how to add support
+for auto-reverting new types of buffers.
+
+First, such buffers must have a suitable @code{revert-buffer-function}
+and @code{buffer-stale-function} defined.
+
 @defvar buffer-stale-function
 The value of this variable specifies a function to call to check
 whether a buffer needs reverting.  The default value only handles
 buffers that are visiting files, by checking their modification time.
-Buffers that are not visiting files require a custom function
-@iftex
-(@pxref{Supporting additional buffers,,, emacs-xtra,  Specialized Emacs Features}).
-@end iftex
-@ifnottex
-(@pxref{Supporting additional buffers,,, emacs}).
-@end ifnottex
+Buffers that are not visiting files require a custom function of one
+optional argument @var{noconfirm}.  The function should return
+non-@code{nil} if the buffer should be reverted.  The buffer is
+current when this function is called.
+
+While this function is mainly intended for use in auto-reverting, it
+could be used for other purposes as well.  For instance, if
+auto-reverting is not enabled, it could be used to warn the user that
+the buffer needs reverting.  The idea behind the @var{noconfirm}
+argument is that it should be @code{t} if the buffer is going to be
+reverted without asking the user and @code{nil} if the function is
+just going to be used to warn the user that the buffer is out of date.
+In particular, for use in auto-reverting, @var{noconfirm} is @code{t}.
+If the function is only going to be used for auto-reverting, you can
+ignore the @var{noconfirm} argument.
+
+If you just want to automatically auto-revert every
+@code{auto-revert-interval} seconds (like the Buffer Menu), use:
+
+@example
+(setq-local buffer-stale-function
+     #'(lambda (&optional noconfirm) 'fast))
+@end example
+
+@noindent
+in the buffer's mode function.
+
+The special return value @samp{fast} tells the caller that the need
+for reverting was not checked, but that reverting the buffer is fast.
+It also tells Auto Revert not to print any revert messages, even if
+@code{auto-revert-verbose} is non-@code{nil}.  This is important, as
+getting revert messages every @code{auto-revert-interval} seconds can
+be very annoying.  The information provided by this return value could
+also be useful if the function is consulted for purposes other than
+auto-reverting.
 @end defvar
+
+Once the buffer has a suitable @code{revert-buffer-function} and
+@code{buffer-stale-function}, several problems usually remain.
+
+The buffer will only auto-revert if it is marked unmodified.  Hence,
+you will have to make sure that various functions mark the buffer
+modified if and only if either the buffer contains information that
+might be lost by reverting, or there is reason to believe that the user
+might be inconvenienced by auto-reverting, because he is actively
+working on the buffer.  The user can always override this by manually
+adjusting the modified status of the buffer.  To support this, calling
+the @code{revert-buffer-function} on a buffer that is marked
+unmodified should always keep the buffer marked unmodified.
+
+It is important to assure that point does not continuously jump around
+as a consequence of auto-reverting.  Of course, moving point might be
+inevitable if the buffer radically changes.
+
+You should make sure that the @code{revert-buffer-function} does not
+print messages that unnecessarily duplicate Auto Revert's own messages,
+displayed if @code{auto-revert-verbose} is @code{t}, and effectively
+override a @code{nil} value for @code{auto-revert-verbose}.  Hence,
+adapting a mode for auto-reverting often involves getting rid of such
+messages.  This is especially important for buffers that automatically
+revert every @code{auto-revert-interval} seconds.
+
+If the new auto-reverting is part of Emacs, you should mention it
+in the documentation string of @code{global-auto-revert-non-file-buffers}.
+
+Similarly, you should document the additions in the Emacs manual.
diff --git a/doc/lispref/display.texi b/doc/lispref/display.texi
index fbf943a08c7..7bf03b8558e 100644
--- a/doc/lispref/display.texi
+++ b/doc/lispref/display.texi
@@ -581,7 +581,7 @@ truncated to fit it.
   The variable @code{max-mini-window-height}, which specifies the
 maximum height for resizing minibuffer windows, also applies to the
 echo area (which is really a special use of the minibuffer window;
-@pxref{Minibuffer Misc}).
+@pxref{Minibuffer Windows}).
 
 @node Warnings
 @section Reporting Warnings
diff --git a/doc/lispref/minibuf.texi b/doc/lispref/minibuf.texi
index 332e72f6402..c7f8ba96e2f 100644
--- a/doc/lispref/minibuf.texi
+++ b/doc/lispref/minibuf.texi
@@ -2323,6 +2323,12 @@ frame's height; an integer specifies the maximum number of lines.  The
 default value is 0.25.
 @end defopt
 
+Note that the values of the above two variables take effect at display
+time, so let-binding them around code which produces echo-area messages
+will not work.  If you want to prevent resizing of minibuffer windows
+when displaying long messages, bind the @code{message-truncate-lines}
+variable instead (@pxref{Echo Area Customization}).
+
 
 @node Minibuffer Contents
 @section Minibuffer Contents
@@ -2450,12 +2456,6 @@ minibuffer window was selected.  If the selected window is not a
 minibuffer window, it returns @code{nil}.
 @end defun
 
-@defopt max-mini-window-height
-This variable specifies the maximum height for resizing minibuffer
-windows.  If a float, it specifies a fraction of the height of the
-frame.  If an integer, it specifies a number of lines.
-@end defopt
-
 @vindex minibuffer-message-timeout
 @defun minibuffer-message string &rest args
 This function displays @var{string} temporarily at the end of the
diff --git a/doc/lispref/os.texi b/doc/lispref/os.texi
index 9352a929a7a..42be60449de 100644
--- a/doc/lispref/os.texi
+++ b/doc/lispref/os.texi
@@ -3042,7 +3042,9 @@ with @samp{-}, or might contain shell metacharacters like @samp{;}.
 Although functions like @code{shell-quote-argument} can help avoid
 this sort of problem, they are not panaceas; for example, on a POSIX
 platform @code{shell-quote-argument} quotes shell metacharacters but
-not leading @samp{-}.  @xref{Shell Arguments}.  Typically it is safer
+not leading @samp{-}.  On MS-Windows, quoting for @samp{%} assumes
+none of the environment variables have @samp{^} in their name.
+@xref{Shell Arguments}.  Typically it is safer
 to use @code{call-process} than a subshell.  @xref{Synchronous
 Processes}.  And it is safer yet to use builtin Emacs functions; for
 example, use @code{(rename-file "@var{a}" "@var{b}" t)} instead of
diff --git a/doc/lispref/processes.texi b/doc/lispref/processes.texi
index 0a3a4617a2e..af177e053cc 100644
--- a/doc/lispref/processes.texi
+++ b/doc/lispref/processes.texi
@@ -728,8 +728,11 @@ Initialize the process query flag to @var{query-flag}.
 @xref{Query Before Exit}.
 
 @item :stop @var{stopped}
-If @var{stopped} is non-@code{nil}, start the process in the
-stopped state.
+If @var{stopped} is non-@code{nil}, start the process in the stopped
+state.  In the stopped state, a pipe process does not accept incoming
+data, but you can send outgoing data.  The stopped state is set by
+@code{stop-process} and cleared by @code{continue-process}
+(@pxref{Signals to Processes}).
 
 @item :filter @var{filter}
 Initialize the process filter to @var{filter}.  If not specified, a