summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2016-05-05 06:39:17 -0700
committerPaul Eggert <eggert@cs.ucla.edu>2016-05-05 06:40:12 -0700
commit5e814e02f0b0b85fa486975eced09e4a7ed8ce5c (patch)
tree0e3d4677bd2e193558ea7245ad176afeae6abd57 /doc
parent3347a733e0778dfefaeabe28ae73f4226236a881 (diff)
downloademacs-5e814e02f0b0b85fa486975eced09e4a7ed8ce5c.tar.gz
Minor doc fixes for quoting
* doc/lispref/control.texi (Signaling Errors): * doc/lispref/display.texi (Displaying Messages): Don’t say that formats “generate”. Try to word more clearly. * etc/NEWS: Coalesce near-duplicate entries.
Diffstat (limited to 'doc')
-rw-r--r--doc/lispref/control.texi13
-rw-r--r--doc/lispref/display.texi13
2 files changed, 14 insertions, 12 deletions
diff --git a/doc/lispref/control.texi b/doc/lispref/control.texi
index 75d8d284623..0cdb03548bf 100644
--- a/doc/lispref/control.texi
+++ b/doc/lispref/control.texi
@@ -1100,12 +1100,13 @@ These examples show typical uses of @code{error}:
error symbol @code{error}, and a list containing the string returned by
@code{format-message}.
-A format that quotes with grave accents and apostrophes @t{`like
-this'} typically generates curved quotes @t{‘like this’}. In
-contrast, a format that quotes with only apostrophes @t{'like this'}
-typically generates two closing curved quotes @t{’like this’}, an
-unusual style in English. @xref{Keys in Documentation}, for how the
-@code{text-quoting-style} variable affects generated quotes.
+The @code{text-quoting-style} variable controls what quotes are
+generated; @xref{Keys in Documentation}. A call using a format like
+@t{"Missing `%s'"} with grave accents and apostrophes typically
+generates a message like @t{"Missing ‘foo’"} with matching curved
+quotes. In contrast, a call using a format like @t{"Missing '%s'"}
+with only apostrophes typically generates a message like @t{"Missing
+’foo’"} with only closing curved quotes, an unusual style in English.
@strong{Warning:} If you want to use your own string as an error message
verbatim, don't just write @code{(error @var{string})}. If @var{string}
diff --git a/doc/lispref/display.texi b/doc/lispref/display.texi
index b0cd8731fe2..181bff09b55 100644
--- a/doc/lispref/display.texi
+++ b/doc/lispref/display.texi
@@ -265,12 +265,13 @@ properties, it is displayed with the specified faces (@pxref{Faces}).
The string is also added to the @file{*Messages*} buffer, but without
text properties (@pxref{Logging Messages}).
-A format that quotes with grave accents and apostrophes @t{`like
-this'} typically generates curved quotes @t{‘like this’}. In
-contrast, a format that quotes with only apostrophes @t{'like this'}
-typically generates two closing curved quotes @t{’like this’}, an
-unusual style in English. @xref{Keys in Documentation}, for how the
-@code{text-quoting-style} variable affects generated quotes.
+The @code{text-quoting-style} variable controls what quotes are
+generated; @xref{Keys in Documentation}. A call using a format like
+@t{"Missing `%s'"} with grave accents and apostrophes typically
+generates a message like @t{"Missing ‘foo’"} with matching curved
+quotes. In contrast, a call using a format like @t{"Missing '%s'"}
+with only apostrophes typically generates a message like @t{"Missing
+’foo’"} with only closing curved quotes, an unusual style in English.
In batch mode, the message is printed to the standard error stream,
followed by a newline.