From 00adee897ac95912cb9ad6bd8a8d161db71945ac Mon Sep 17 00:00:00 2001 From: Stefan Kangas Date: Sun, 21 Jul 2024 16:33:08 +0200 Subject: [PATCH] ; Fix punctuation in docs --- doc/emacs/custom.texi | 2 +- doc/emacs/display.texi | 2 +- doc/emacs/fortran-xtra.texi | 2 +- doc/emacs/frames.texi | 2 +- doc/emacs/trouble.texi | 2 +- doc/emacs/vc1-xtra.texi | 2 +- doc/lispintro/emacs-lisp-intro.texi | 8 +-- doc/lispref/commands.texi | 2 +- doc/lispref/display.texi | 2 +- doc/lispref/files.texi | 4 +- doc/lispref/modes.texi | 2 +- doc/lispref/package.texi | 4 +- doc/lispref/positions.texi | 2 +- doc/lispref/processes.texi | 2 +- doc/lispref/searching.texi | 4 +- doc/lispref/sequences.texi | 2 +- doc/lispref/streams.texi | 2 +- doc/lispref/variables.texi | 2 +- doc/man/etags.1 | 2 +- doc/misc/auth.texi | 12 +++-- doc/misc/autotype.texi | 2 +- doc/misc/bovine.texi | 2 +- doc/misc/calc.texi | 84 ++++++++++++++--------------- doc/misc/cc-mode.texi | 8 +-- doc/misc/cl.texi | 4 +- doc/misc/dbus.texi | 4 +- doc/misc/ebrowse.texi | 6 +-- doc/misc/ede.texi | 2 +- doc/misc/ediff.texi | 76 +++++++++++++------------- doc/misc/efaq-w32.texi | 36 ++++++------- doc/misc/efaq.texi | 8 +-- doc/misc/eglot.texi | 4 +- doc/misc/emacs-mime.texi | 2 +- doc/misc/ert.texi | 10 ++-- doc/misc/eshell.texi | 12 ++--- doc/misc/eudc.texi | 40 +++++++------- doc/misc/flymake.texi | 2 +- doc/misc/forms.texi | 22 ++++---- doc/misc/gnus-faq.texi | 26 ++++----- doc/misc/gnus.texi | 44 +++++++-------- doc/misc/htmlfontify.texi | 2 +- doc/misc/idlwave.texi | 16 +++--- doc/misc/info.texi | 2 +- doc/misc/message.texi | 14 ++--- doc/misc/modus-themes.org | 50 ++++++++--------- doc/misc/newsticker.texi | 20 +++---- doc/misc/nxml-mode.texi | 82 ++++++++++++++-------------- doc/misc/org.org | 22 ++++---- doc/misc/pcl-cvs.texi | 2 +- doc/misc/rcirc.texi | 2 +- doc/misc/reftex.texi | 24 ++++----- doc/misc/sc.texi | 2 +- doc/misc/ses.texi | 56 +++++++++---------- doc/misc/speedbar.texi | 2 +- doc/misc/todo-mode.texi | 4 +- doc/misc/transient.texi | 10 ++-- doc/misc/use-package.texi | 4 +- doc/misc/vhdl-mode.texi | 28 +++++----- doc/misc/vip.texi | 18 +++---- doc/misc/viper.texi | 40 +++++++------- doc/misc/widget.texi | 4 +- doc/misc/wisent.texi | 4 +- 62 files changed, 433 insertions(+), 431 deletions(-) diff --git a/doc/emacs/custom.texi b/doc/emacs/custom.texi index a385d06bb1d..1527e42bbfe 100644 --- a/doc/emacs/custom.texi +++ b/doc/emacs/custom.texi @@ -2044,7 +2044,7 @@ sequences. For example, to bind @kbd{C-c h} to the string @end example Non-@acronym{ASCII} characters can be specified directly in the -string. To bind to e.g. @samp{ol@'a}, use: +string. To bind to e.g. @samp{ol@'a}, use: @example (keymap-global-set "C-c h" (key-description "ol@'a")) diff --git a/doc/emacs/display.texi b/doc/emacs/display.texi index 8f22e3c88da..88520874c8e 100644 --- a/doc/emacs/display.texi +++ b/doc/emacs/display.texi @@ -2198,7 +2198,7 @@ The line numbers are displayed in a special face @code{line-number}. The current line number is displayed in a different face, @code{line-number-current-line}, so you can make the current line's number have a distinct appearance, which will help locating the line -showing point. Additional faces @code{line-number-major-tick} and +showing point. Additional faces @code{line-number-major-tick} and @code{line-number-minor-tick} can be used to highlight the line numbers of lines which are a multiple of certain numbers. Customize @code{display-line-numbers-major-tick} and diff --git a/doc/emacs/fortran-xtra.texi b/doc/emacs/fortran-xtra.texi index 5225dfccbd0..1884ee76219 100644 --- a/doc/emacs/fortran-xtra.texi +++ b/doc/emacs/fortran-xtra.texi @@ -124,7 +124,7 @@ check the outermost block since that may be incomplete. @findex f90-beginning-of-block @item C-M-p Move to the start of the current code block -(@code{fortran-beginning-of-block}/@code{f90-beginning-of-block}). This +(@code{fortran-beginning-of-block}/@code{f90-beginning-of-block}). This is like @code{fortran-end-of-block}, but moves backwards. @end table diff --git a/doc/emacs/frames.texi b/doc/emacs/frames.texi index e1fbf9768af..b5f2c5f5e84 100644 --- a/doc/emacs/frames.texi +++ b/doc/emacs/frames.texi @@ -1543,7 +1543,7 @@ After customizing the variable @code{tab-bar-select-tab-modifiers} to specify one or more @var{modifier} keys, you can select a tab by its ordinal number using one of the specified modifiers in combination with the tab number to select. The number 9 can be used to select the -last tab. You can select any modifiers supported by Emacs, +last tab. You can select any modifiers supported by Emacs, @pxref{Modifier Keys}. To display the tab number alongside the tab name, you can customize another variable @code{tab-bar-tab-hints}. This will help you decide which numerical key to press to select the diff --git a/doc/emacs/trouble.texi b/doc/emacs/trouble.texi index e4993fb0014..c385d6b0b3d 100644 --- a/doc/emacs/trouble.texi +++ b/doc/emacs/trouble.texi @@ -1488,7 +1488,7 @@ the Emacs Lisp Reference Manual @cindex coding standards for Emacs submissions Contributed code should follow the GNU Coding Standards -@url{https://www.gnu.org/prep/standards/}. This may also be available +@url{https://www.gnu.org/prep/standards/}. This may also be available in info on your system. If it doesn't, we'll need to find someone to fix the code before we diff --git a/doc/emacs/vc1-xtra.texi b/doc/emacs/vc1-xtra.texi index 303efa05d82..8897129d1b0 100644 --- a/doc/emacs/vc1-xtra.texi +++ b/doc/emacs/vc1-xtra.texi @@ -177,7 +177,7 @@ current directory as a tag named @var{name} @findex vc-retrieve-tag @item C-x v r @var{name} @key{RET} For all registered files at or below the current directory level, -retrieve the tagged revision @var{name}. This command will switch to a +retrieve the tagged revision @var{name}. This command will switch to a branch if @var{name} is a branch name and your VCS distinguishes branches from tags. (@code{vc-retrieve-tag}). diff --git a/doc/lispintro/emacs-lisp-intro.texi b/doc/lispintro/emacs-lisp-intro.texi index 4649cd59962..bc4dc31bf4c 100644 --- a/doc/lispintro/emacs-lisp-intro.texi +++ b/doc/lispintro/emacs-lisp-intro.texi @@ -130,7 +130,7 @@ Boston, MA 02110-1301 USA @end iftex @ifnottex -Printed copies available from @uref{https://shop.fsf.org/}. Published by: +Printed copies available from @uref{https://shop.fsf.org/}. Published by: @example GNU Press, https://www.fsf.org/licensing/gnu-press/ @@ -1969,7 +1969,7 @@ argument is the string of characters, the second and third arguments are numbers that indicate the beginning (inclusive) and end (exclusive) of the substring. The numbers are a count of the number of characters (including spaces and punctuation) from the beginning of -the string. Note that the characters in a string are numbered from +the string. Note that the characters in a string are numbered from zero, not one. @need 800 @@ -5314,7 +5314,7 @@ Looking at the @code{let*} expression in @code{append-to-buffer}: @noindent we see that @code{append-to} is bound to the value returned by the -@w{@code{(get-buffer-create buffer)}}. On the next line, +@w{@code{(get-buffer-create buffer)}}. On the next line, @code{append-to} is used as an argument to @code{get-buffer-window-list}; this would not be possible with the @code{let} expression. Note that @code{point} is automatically bound @@ -16099,7 +16099,7 @@ placing point somewhere in the buffer, typing @kbd{M-:}, typing the and then typing @key{RET}. This causes Emacs to evaluate the expression in the minibuffer, but to use as the value of point the position of point in the @file{*scratch*} buffer. (@kbd{M-:} is the -key binding for @code{eval-expression}. Also, @code{nil} does not +key binding for @code{eval-expression}. Also, @code{nil} does not appear in the @file{*scratch*} buffer since the expression is evaluated in the minibuffer.) diff --git a/doc/lispref/commands.texi b/doc/lispref/commands.texi index a9da6c75367..60de1cc1183 100644 --- a/doc/lispref/commands.texi +++ b/doc/lispref/commands.texi @@ -1741,7 +1741,7 @@ this is @code{nil}. @item @var{dx}, @var{dy} These are the pixel offsets of the click relative to the top left corner of the @var{object}'s glyph that is the nearest one to the -click. The relevant @var{object}s can be either a buffer, or a string, +click. The relevant @var{object}s can be either a buffer, or a string, or an image, see above. If @var{object} is @code{nil} or a string, the coordinates are relative to the top left corner of the character glyph clicked on. Note that the offsets are always zero on text-mode diff --git a/doc/lispref/display.texi b/doc/lispref/display.texi index 139fdcfc101..81e534a5357 100644 --- a/doc/lispref/display.texi +++ b/doc/lispref/display.texi @@ -2771,7 +2771,7 @@ width of the vertical and horizontal lines to draw; they default to (1 . 1). A negative horizontal or vertical width @minus{}@var{n} means to draw a line of width @var{n} that occupies the space of the underlying text, thus avoiding any increase in the character height or -width. For simplification the width could be specified with only a +width. For simplification the width could be specified with only a single number @var{n} instead of a list, such case is equivalent to @code{((abs @var{n}) . @var{n})}. diff --git a/doc/lispref/files.texi b/doc/lispref/files.texi index 1a8f3812f1e..70db8521481 100644 --- a/doc/lispref/files.texi +++ b/doc/lispref/files.texi @@ -2708,7 +2708,7 @@ file names (@pxref{Magic File Names}). @defmac file-name-unquote name This macro removes the quotation prefix @samp{/:} from the file -@var{name}, if any. If @var{name} is a remote file name, the local +@var{name}, if any. If @var{name} is a remote file name, the local part of @var{name} is unquoted. @end defmac @@ -2740,7 +2740,7 @@ This function creates a temporary file and returns its name. Emacs creates the temporary file's name by adding to @var{prefix} some random characters that are different in each Emacs job. The result is guaranteed to be a newly created file, containing @var{text} if that's -given as a string and empty otherwise. On MS-DOS, this function can +given as a string and empty otherwise. On MS-DOS, this function can truncate @var{prefix} to fit into the 8+3 file-name limits. If @var{prefix} is a relative file name, it is expanded against @code{temporary-file-directory}. diff --git a/doc/lispref/modes.texi b/doc/lispref/modes.texi index f3d4f5347b3..7c7823b5f9b 100644 --- a/doc/lispref/modes.texi +++ b/doc/lispref/modes.texi @@ -4530,7 +4530,7 @@ and a few other such modes) has been made more generic over the years, so if your language seems somewhat similar to one of those languages, you might try to use that engine. @c FIXME: documentation? Another one is SMIE which takes an approach in the spirit -of Lisp sexps and adapts it to non-Lisp languages. Yet another one is +of Lisp sexps and adapts it to non-Lisp languages. Yet another one is to rely on a full-blown parser, for example, the tree-sitter library. @menu diff --git a/doc/lispref/package.texi b/doc/lispref/package.texi index 60cff9d1891..eb0b4ca213c 100644 --- a/doc/lispref/package.texi +++ b/doc/lispref/package.texi @@ -387,7 +387,7 @@ following queries: @table @asis @item archive-contents -Return a lisp form describing the archive contents. The form is a list +Return a lisp form describing the archive contents. The form is a list of 'package-desc' structures (see @file{package.el}), except the first element of the list is the archive version. @@ -398,7 +398,7 @@ Return the long description of the package. Return the signature for the file. @item -Return the file. This will be the tarball for a multi-file +Return the file. This will be the tarball for a multi-file package, or the single file for a simple package. @end table diff --git a/doc/lispref/positions.texi b/doc/lispref/positions.texi index ead7833af61..37cfe264157 100644 --- a/doc/lispref/positions.texi +++ b/doc/lispref/positions.texi @@ -450,7 +450,7 @@ in the buffer, or in the region if the region is active. @cindex line number This function returns the line number in the current buffer corresponding to the buffer position @var{pos}. If @var{pos} is -@code{nil} or omitted, the current buffer position is used. If +@code{nil} or omitted, the current buffer position is used. If @var{absolute} is @code{nil}, the default, counting starts at @code{(point-min)}, so the value refers to the contents of the accessible portion of the (potentially narrowed) buffer. If diff --git a/doc/lispref/processes.texi b/doc/lispref/processes.texi index c5fbb0fb818..53468e0d252 100644 --- a/doc/lispref/processes.texi +++ b/doc/lispref/processes.texi @@ -135,7 +135,7 @@ stream to a different destination. @cindex program arguments All three of the subprocess-creating functions allow specifying -command-line arguments for the process to run. For @code{call-process} +command-line arguments for the process to run. For @code{call-process} and @code{call-process-region}, these come in the form of a @code{&rest} argument, @var{args}. For @code{make-process}, both the program to run and its command-line arguments are specified as a list diff --git a/doc/lispref/searching.texi b/doc/lispref/searching.texi index 6e3680bdb4f..7cefd581afb 100644 --- a/doc/lispref/searching.texi +++ b/doc/lispref/searching.texi @@ -1771,7 +1771,7 @@ required for @code{rx-to-string} to work. Example: Another difference from @code{rx-let} is that the @var{bindings} are dynamically scoped, and thus also available in functions called from -@var{body}. However, they are not visible inside functions defined in +@var{body}. However, they are not visible inside functions defined in @var{body}. @end defmac @@ -1919,7 +1919,7 @@ symptoms less likely and help alleviate problems that do arise. @itemize @item Anchor regexps at the beginning of a line, string or buffer using -zero-width assertions (@samp{^} and @code{\`}). This takes advantage +zero-width assertions (@samp{^} and @code{\`}). This takes advantage of fast paths in the implementation and can avoid futile matching attempts. Other zero-width assertions may also bring benefits by causing a match to fail early. diff --git a/doc/lispref/sequences.texi b/doc/lispref/sequences.texi index d5695e4c83d..9b0a0d74f30 100644 --- a/doc/lispref/sequences.texi +++ b/doc/lispref/sequences.texi @@ -937,7 +937,7 @@ use instead of the default @code{equal}. @defun seq-set-equal-p sequence1 sequence2 &optional testfn This function checks whether @var{sequence1} and @var{sequence2} -contain the same elements, regardless of the order. If the optional +contain the same elements, regardless of the order. If the optional argument @var{testfn} is non-@code{nil}, it is a function of two arguments to use instead of the default @code{equal}. diff --git a/doc/lispref/streams.texi b/doc/lispref/streams.texi index 86ec82b66a1..a48e6380d32 100644 --- a/doc/lispref/streams.texi +++ b/doc/lispref/streams.texi @@ -970,7 +970,7 @@ you can use, see the variable's documentation string. @defvar print-integers-as-characters When this variable is non-@code{nil}, integers that represent graphic base characters will be printed using Lisp character syntax -(@pxref{Basic Char Syntax}). Other numbers are printed the usual way. +(@pxref{Basic Char Syntax}). Other numbers are printed the usual way. For example, the list @code{(4 65 -1 10)} would be printed as @samp{(4 ?A -1 ?\n)}. diff --git a/doc/lispref/variables.texi b/doc/lispref/variables.texi index 0ed1936cd84..76f15b2595c 100644 --- a/doc/lispref/variables.texi +++ b/doc/lispref/variables.texi @@ -2613,7 +2613,7 @@ compatibility. You can do this with @code{defvaralias}. @defun defvaralias new-alias base-variable &optional docstring This function defines the symbol @var{new-alias} as a variable alias -for symbol @var{base-variable}. This means that retrieving the value +for symbol @var{base-variable}. This means that retrieving the value of @var{new-alias} returns the value of @var{base-variable}, and changing the value of @var{new-alias} changes the value of @var{base-variable}. The two aliased variable names always share the diff --git a/doc/man/etags.1 b/doc/man/etags.1 index c567c51d7ef..9b8df50a6bb 100644 --- a/doc/man/etags.1 +++ b/doc/man/etags.1 @@ -171,7 +171,7 @@ of \- means standard output; overrides default \fBTAGS\fP or \fBtags\fP. Make tags based on regexp matching for the files following this option, in addition to the tags made with the standard parsing based on -language. May be freely intermixed with filenames and the \fB\-R\fP +language. May be freely intermixed with filenames and the \fB\-R\fP option. The regexps are cumulative, i.e., each such option will add to the previous ones. The regexps are of one of the forms: .br diff --git a/doc/misc/auth.texi b/doc/misc/auth.texi index 8d802be535c..bb4beb38837 100644 --- a/doc/misc/auth.texi +++ b/doc/misc/auth.texi @@ -136,12 +136,12 @@ You can use spaces inside a password or other token by surrounding the token with either single or double quotes. You can use apostrophes inside a password or other token by -surrounding it with double quotes, e.g., @code{"he'llo"}. Similarly you +surrounding it with double quotes, e.g., @code{"he'llo"}. Similarly you can use double quotes inside a password or other token by surrounding -it with apostrophes, e.g., @code{'he"llo'}. You can't mix both (so a +it with apostrophes, e.g., @code{'he"llo'}. You can't mix both (so a password or other token can't have both apostrophes and double quotes). -All this is optional. You could just say (but we don't recommend it, +All this is optional. You could just say (but we don't recommend it, we're just showing that it's possible) @example @@ -267,7 +267,7 @@ earlier. Since Tramp has about 88 connection methods, this may be necessary if you have an unusual (see earlier comment on those) setup. The netrc format is directly translated into JSON, if you are into -that sort of thing. Just point to a JSON file with entries like this: +that sort of thing. Just point to a JSON file with entries like this: @example [ @@ -501,7 +501,9 @@ The username can also be expressed as a prefix, separated from the host with an at-sign (@code{@@}). @item gnu.org:22.gpg -The port (aka. service) to match can only be expressed after the host and separated with a colon (@code{:}). The separator can be changed through the @code{auth-source-pass-port-separator} variable. +The port (aka. service) to match can only be expressed after the host +and separated with a colon (@code{:}). The separator can be changed +through the @code{auth-source-pass-port-separator} variable. @item gnu.org:22/rms.gpg diff --git a/doc/misc/autotype.texi b/doc/misc/autotype.texi index d927816c492..4bd07c8d312 100644 --- a/doc/misc/autotype.texi +++ b/doc/misc/autotype.texi @@ -290,7 +290,7 @@ be inserted. It can also be a function, which allows doing various things. The function can simply insert some text, indeed, it can be skeleton command (@pxref{Using Skeletons}). It can be a lambda function which will for example conditionally -call another function. Or it can even reset the mode for the buffer. If you +call another function. Or it can even reset the mode for the buffer. If you want to perform several such actions in order, you use a vector, i.e., several of the above elements between square brackets (@samp{[@r{@dots{}}]}). diff --git a/doc/misc/bovine.texi b/doc/misc/bovine.texi index 5cef9ffbb93..f4eb0784cb2 100644 --- a/doc/misc/bovine.texi +++ b/doc/misc/bovine.texi @@ -346,7 +346,7 @@ semantic list. @item (EXPANDFULL @var{$1} @var{nonterminal} @var{depth}) Is like @code{EXPAND}, except that the parser will iterate over @var{nonterminal} until there are no more matches. (The same way the -parser iterates over the starting rule (@pxref{Starting Rules}). This +parser iterates over the starting rule (@pxref{Starting Rules}). This lets you have much simpler rules in this specific case, and also lets you have positional information in the returned tokens, and error skipping. diff --git a/doc/misc/calc.texi b/doc/misc/calc.texi index 54909c130c3..384ad889ae1 100644 --- a/doc/misc/calc.texi +++ b/doc/misc/calc.texi @@ -355,7 +355,7 @@ To print the Calc manual in one huge tome, you will need the Emacs source, which contains the source code to this manual, @file{calc.texi}. Change to the @file{doc/misc} subdirectory of the Emacs source distribution, which contains source code for this manual, -and type @kbd{make calc.pdf}. (Don't worry if you get some ``overfull +and type @kbd{make calc.pdf}. (Don't worry if you get some ``overfull box'' warnings while @TeX{} runs.) The result will be this entire manual as a pdf file. @end ifnottex @@ -524,7 +524,7 @@ matrix into a @infoline 2x3 matrix. Type @w{@kbd{v u}} to unpack the rows into two separate vectors. Now type @w{@kbd{V R + @key{TAB} V R +}} to compute the sums -of the two original columns. (There is also a special +of the two original columns. (There is also a special grab-and-sum-columns command, @kbd{C-x * :}.) @strong{Units conversion.} Units are entered algebraically. @@ -929,7 +929,7 @@ is Calc has added annotations to the file to help it remember the modes that were used for this formula. They are formatted like comments in the @TeX{} typesetting language, just in case you are using @TeX{} or -@LaTeX{}. (In this example @TeX{} is not being used, so you might want +@LaTeX{}. (In this example @TeX{} is not being used, so you might want to move these comments up to the top of the file or otherwise put them out of the way.) @@ -1174,7 +1174,7 @@ that arbitrary-size integers were just as easy as large integers. Arbitrary floating-point precision was the logical next step. Also, since the large integer arithmetic was there anyway it seemed only fair to give the user direct access to it, which in turn made it -practical to support fractions as well as floats. All these features +practical to support fractions as well as floats. All these features inspired me to look around for other data types that might be worth having. @@ -5762,7 +5762,7 @@ which in algebraic notation is written like @samp{ninteg(f(t), t, 0, x)} with any integrand @samp{f(t)}. Define a @kbd{z s} command and @code{Si} function that implement this. You will need to edit the default argument list a bit. As a test, @samp{Si(1)} should return -0.946083. (If you don't get this answer, you might want to check that +0.946083. (If you don't get this answer, you might want to check that Calc is in Radians mode. Also, @code{ninteg} will run a lot faster if you reduce the precision to, say, six digits beforehand.) @xref{Programming Answer 1, 1}. (@bullet{}) @@ -9758,7 +9758,7 @@ by a zero) resets the Calculator to its initial state. This clears the stack, resets all the modes to their initial values (the values that were saved with @kbd{m m} (@code{calc-save-modes})), clears the caches (@pxref{Caches}), and so on. (It does @emph{not} erase the -values of any variables.) With an argument of 0, Calc will be reset to +values of any variables.) With an argument of 0, Calc will be reset to its default state; namely, the modes will be given their default values. With a positive prefix argument, @kbd{C-x * 0} preserves the contents of the stack but resets everything else to its initial state; with a @@ -10254,7 +10254,7 @@ specified number of operations. When the Calculator is quit, as with the @kbd{q} (@code{calc-quit}) command, the undo history will be truncated to the length of the customizable variable @code{calc-undo-length} (@pxref{Customizing Calc}), which by default -is @expr{100}. (Recall that @kbd{C-x * c} is synonymous with +is @expr{100}. (Recall that @kbd{C-x * c} is synonymous with @code{calc-quit} while inside the Calculator; this also truncates the undo history.) @@ -11050,8 +11050,8 @@ calendar. Some calendars attempt to mimic the historical situation by using the Gregorian calendar for recent dates and the Julian calendar for older -dates. The @code{cal} program in most Unix implementations does this, -for example. While January 1 wasn't always the beginning of a calendar +dates. The @code{cal} program in most Unix implementations does this, +for example. While January 1 wasn't always the beginning of a calendar year, these hybrid calendars still use January 1 as the beginning of the year even for older dates. The customizable variable @code{calc-gregorian-switch} (@pxref{Customizing Calc}) can be set to @@ -11405,7 +11405,7 @@ means a variable is random, and its value could be anything but is ``probably'' within one @texline @math{\sigma} @infoline @var{sigma} -of the mean value @expr{x}. An interval +of the mean value @expr{x}. An interval `@tfn{[}@var{a} @tfn{..@:} @var{b}@tfn{]}' means a variable's value is unknown, but guaranteed to lie in the specified range. Error forms are statistical or ``average case'' approximations; @@ -11862,7 +11862,7 @@ any portion of a vector or formula on the stack. @cindex Moving stack entries The command @kbd{C-x C-t} (@code{calc-transpose-lines}) will transpose the stack object determined by the point with the stack object at the -next higher level. For example, with @samp{10 20 30 40 50} on the +next higher level. For example, with @samp{10 20 30 40 50} on the stack and the point on the line containing @samp{30}, @kbd{C-x C-t} creates @samp{10 20 40 30 50}. More generally, @kbd{C-x C-t} acts on the stack objects determined by the current point (and mark) similar @@ -11871,7 +11871,7 @@ lines. With argument @var{n}, @kbd{C-x C-t} will move the stack object at the level above the current point and move it past N other objects; for example, with @samp{10 20 30 40 50} on the stack and the point on the line containing @samp{30}, @kbd{C-u 2 C-x C-t} creates -@samp{10 40 20 30 50}. With an argument of 0, @kbd{C-x C-t} will switch +@samp{10 40 20 30 50}. With an argument of 0, @kbd{C-x C-t} will switch the stack objects at the levels determined by the point and the mark. @node Editing Stack Entries @@ -12062,14 +12062,14 @@ the stack contains the sole number 5, but after @kbd{2 @key{RET} 3 K +}, the stack contains the arguments and the result: @samp{2 3 5}. With the exception of keyboard macros, this works for all commands that -take arguments off the stack. (To avoid potentially unpleasant behavior, +take arguments off the stack. (To avoid potentially unpleasant behavior, a @kbd{K} prefix before a keyboard macro will be ignored. A @kbd{K} prefix called @emph{within} the keyboard macro will still take effect.) As another example, @kbd{K a s} simplifies a formula, pushing the simplified version of the formula onto the stack after the original formula (rather than replacing the original formula). Note that you could get the same effect by typing @kbd{@key{RET} a s}, copying the -formula and then simplifying the copy. One difference is that for a very +formula and then simplifying the copy. One difference is that for a very large formula the time taken to format the intermediate copy in @kbd{@key{RET} a s} could be noticeable; @kbd{K a s} would avoid this extra work. @@ -13171,7 +13171,7 @@ Calc can display @expr{w}-bit integers using two's complement notation, although this is most useful with the binary, octal and hexadecimal display modes. This option is selected by using the @kbd{O} option prefix before setting the display radix, and a negative word -size might be appropriate (@pxref{Binary Functions}). In two's +size might be appropriate (@pxref{Binary Functions}). In two's complement notation, the integers in the (nearly) symmetric interval from @texline @math{-2^{w-1}} @@ -13502,7 +13502,7 @@ date representation, this week goes from 2013-W01-1 (December 31, All three ISO 8601 representations arrange the numbers from most significant to least significant; as well as being unambiguous representations, they are easy to sort since chronological order in -this formats corresponds to lexicographical order. The hyphens are +this formats corresponds to lexicographical order. The hyphens are sometimes omitted. The ISO 8601 standard uses a 24 hour clock; a particular time is @@ -13744,7 +13744,7 @@ order), then all other characters are ignored and this information determines the date. Otherwise, all words and numbers are isolated from the string; other characters are ignored. All words must be either month names or day-of-week names (the latter of which are -ignored). Names can be written in full or as three-letter +ignored). Names can be written in full or as three-letter abbreviations. Large numbers, or numbers with @samp{+} or @samp{-} signs, @@ -14205,9 +14205,9 @@ quotients are written using @code{\over} in @TeX{} mode (as in @code{\choose} in @TeX{} mode (as in @code{@{a \choose b@}}) and @code{\binom} in @LaTeX{} mode (as in @code{\binom@{a@}@{b@}}). Interval forms are written with @code{\ldots}, and error forms are -written with @code{\pm}. Absolute values are written as in +written with @code{\pm}. Absolute values are written as in @samp{|x + 1|}, and the floor and ceiling functions are written with -@code{\lfloor}, @code{\rfloor}, etc. The words @code{\left} and +@code{\lfloor}, @code{\rfloor}, etc. The words @code{\left} and @code{\right} are ignored when reading formulas in @TeX{} and @LaTeX{} modes. Both @code{inf} and @code{uinf} are written as @code{\infty}; when read, @code{\infty} always translates to @code{inf}. @@ -16290,7 +16290,7 @@ interpretations; the expression @samp{a/b*c} should be written @samp{(a/b)*c} or @samp{a/(b*c)}, as appropriate. Without the parentheses, Calc will interpret @samp{a/b*c} as @samp{a/(b*c)}, since in algebraic entry Calc gives division a lower precedence than -multiplication. (This is not standard across all computer languages, and +multiplication. (This is not standard across all computer languages, and Calc may change the precedence depending on the language mode being used. @xref{Language Modes}.) This default ordering can be changed by setting the customizable variable @code{calc-multiplication-has-precedence} to @@ -17456,7 +17456,7 @@ converting into a generalized time zone (see below). The Lisp function @code{math-prev-weekday-in-month} is useful for daylight saving computations. This is an internal version of the user-level @code{pwday} function described in the previous -section. It takes four arguments: The floating-point date value, +section. It takes four arguments: The floating-point date value, the corresponding six-element date list, the day-of-month number, and the weekday number (0--6). @@ -20150,7 +20150,7 @@ that the counts in the result vector don't add up to the length of the input vector.) If no prefix is given, then you will be prompted for a vector which -will be used to determine the bins. (If a positive integer is given at +will be used to determine the bins. (If a positive integer is given at this prompt, it will be still treated as if it were given as a prefix.) Each bin will consist of the interval of numbers closest to the corresponding number of this new vector; if the vector @@ -21636,7 +21636,7 @@ to @noindent Every character not part of the sub-formula @samp{b} has been changed -to a dot. (If the customizable variable +to a dot. (If the customizable variable @code{calc-highlight-selections-with-faces} is non-@code{nil}, then the characters not part of the sub-formula are de-emphasized by using a less noticeable face instead of using dots. @pxref{Displaying Selections}.) @@ -22837,12 +22837,12 @@ suitable numbers. This section describes all simplifications that are performed by the algebraic simplification mode, which is the default simplification mode. If you have switched to a different simplification mode, you can -switch back with the @kbd{m A} command. Even in other simplification +switch back with the @kbd{m A} command. Even in other simplification modes, the @kbd{a s} command will use these algebraic simplifications to simplify the formula. There is a variable, @code{AlgSimpRules}, in which you can put rewrites -to be applied. Its use is analogous to @code{EvalRules}, +to be applied. Its use is analogous to @code{EvalRules}, but without the special restrictions. Basically, the simplifier does @samp{@w{a r} AlgSimpRules} with an infinite repeat count on the whole expression being simplified, then it traverses the expression applying @@ -22991,7 +22991,7 @@ function; for example, @expr{1/@tfn{sec}(x)} is simplified to hyperbolic functions are also handled. Trigonometric functions of their inverse functions are -simplified. The expression @expr{@tfn{sin}(@tfn{arcsin}(x))} is +simplified. The expression @expr{@tfn{sin}(@tfn{arcsin}(x))} is simplified to @expr{x}, and similarly for @code{cos} and @code{tan}. Trigonometric functions of inverses of different trigonometric functions can also be simplified, as in @expr{@tfn{sin}(@tfn{arccos}(x))} @@ -27646,7 +27646,7 @@ simplifications. Most of the special limitations for @code{EvalRules} don't apply to @code{AlgSimpRules}. Calc simply does an @kbd{a r AlgSimpRules} command with an infinite repeat count as the first step of algebraic -simplifications. It then applies its own built-in simplifications +simplifications. It then applies its own built-in simplifications throughout the formula, and then repeats these two steps (along with applying the default simplifications) until no further changes are possible. @@ -27883,7 +27883,7 @@ while typing @kbd{u c au/yr @key{RET}} produces If the units you request are inconsistent with the original units, the number will be converted into your units times whatever ``remainder'' units are left over. For example, converting @samp{55 mph} into acres -produces @samp{6.08e-3 acre / (m s)}. Remainder units are expressed in terms of +produces @samp{6.08e-3 acre / (m s)}. Remainder units are expressed in terms of ``fundamental'' units like @samp{m} and @samp{s}, regardless of the input units. @@ -28257,7 +28257,7 @@ is defined to be @infoline @math{10 log10(P1/P0) dB}. @texline @math{10 \log_{10}(P_{1}/P_{0}) {\rm dB}}. (The factor of 10 is because a decibel, as its name implies, is -one-tenth of a bel. The bel, named after Alexander Graham Bell, was +one-tenth of a bel. The bel, named after Alexander Graham Bell, was considered to be too large of a unit and was effectively replaced by the decibel.) If @math{F} is a field quantity with power @math{P=k F^2}, then a reference quantity of @@ -28353,10 +28353,10 @@ capital @kbd{O} prefix is used. @tindex lufquant The @kbd{l q} (@code{calc-lu-quant}) [@code{lupquant}] command computes the power quantity corresponding to a given number of -logarithmic units. With the capital @kbd{O} prefix, @kbd{O l q}, the -reference level will be read from the top of the stack. (In an +logarithmic units. With the capital @kbd{O} prefix, @kbd{O l q}, the +reference level will be read from the top of the stack. (In an algebraic formula, @code{lupquant} can be given an optional second -argument which will be used for the reference level.) For example, +argument which will be used for the reference level.) For example, @code{20 dB @key{RET} l q} will return @code{100 mW}; @code{20 dB @key{RET} 4 W @key{RET} O l q} will return @code{400 W}. The @kbd{H l q} [@code{lufquant}] command behaves like @kbd{l q} but @@ -28469,7 +28469,7 @@ The @kbd{l *} (@code{calc-lu-times}) [@code{lupmul}] and @kbd{H l *} [@code{lufmul}] commands will ``multiply'' a logarithmic unit by a number; the @kbd{l /} (@code{calc-lu-divide}) [@code{lupdiv}] and @kbd{H l /} [@code{lufdiv}] commands will ``divide'' a logarithmic -unit by a number. Note that the reference quantities don't play a role +unit by a number. Note that the reference quantities don't play a role in this arithmetic. @node Musical Notes @@ -28528,7 +28528,7 @@ example, @code{500 Hz} gets converted to @tindex midi The @kbd{l m} (@code{calc-midi}) [@code{midi}] command converts either a frequency or a note given in scientific pitch notation to the -corresponding midi number. For example, @code{C_6} gets converted to 84 +corresponding midi number. For example, @code{C_6} gets converted to 84 and @code{440 Hz} to 69. @kindex l f @@ -28536,7 +28536,7 @@ and @code{440 Hz} to 69. @tindex freq The @kbd{l f} (@code{calc-freq}) [@code{freq}] command converts either either a midi number or a note given in scientific pitch notation to -the corresponding frequency. For example, @code{Asharp_2 + 30 cents} +the corresponding frequency. For example, @code{Asharp_2 + 30 cents} gets converted to @code{118.578040134 Hz} and @code{55} to @code{195.99771799 Hz}. @@ -29530,7 +29530,7 @@ will be computed for the surface. Data values in the graph of a function are normally computed to a precision of five digits, regardless of the current precision at the -time. This is usually more than adequate, but there are cases where +time. This is usually more than adequate, but there are cases where it will not be. For example, plotting @expr{1 + x} with @expr{x} in the interval @samp{[0 ..@: 1e-6]} will round all the data points down to 1.0! Putting the command @samp{set precision @var{n}} in the @@ -29975,7 +29975,7 @@ register will be deleted from the Calc buffer. It is possible to add additional stack entries to a register. The command @kbd{M-x calc-append-to-register} will prompt for a register, then add the stack entries in the region to the end of the register -contents. The command @kbd{M-x calc-prepend-to-register} will +contents. The command @kbd{M-x calc-prepend-to-register} will similarly prompt for a register and add the stack entries in the region to the beginning of the register contents. Both commands take @kbd{C-u} arguments, which will cause the region to be deleted after being @@ -30620,7 +30620,7 @@ like most Calc commands, but rather in regular editing buffers that are visiting your own files. Calc will try to guess an appropriate language based on the major mode -of the editing buffer. (@xref{Language Modes}.) If the current buffer is +of the editing buffer. (@xref{Language Modes}.) If the current buffer is in @code{latex-mode}, for example, Calc will set its language to @LaTeX{}. Similarly, Calc will use @TeX{} language for @code{tex-mode}, @code{plain-tex-mode} and @code{context-mode}, C language for @@ -30657,7 +30657,7 @@ on their own separate lines or in-line with the formula. If you give a positive or negative numeric prefix argument, Calc instead uses the current point as one end of the formula, and includes that many lines forward or backward (respectively, including the current -line). Explicit delimiters are not necessary in this case. +line). Explicit delimiters are not necessary in this case. With a prefix argument of zero, Calc uses the current region (delimited by point and mark) instead of formula delimiters. With a prefix @@ -31189,7 +31189,7 @@ use @kbd{C-x * u} to update the buffer by hand. @noindent The mode settings can be changed while Calc is in embedded mode, but by default they will revert to their original values when embedded mode -is ended. However, the modes saved when the mode-recording mode is +is ended. However, the modes saved when the mode-recording mode is @code{Save} (see below) and the modes in effect when the @kbd{m e} (@code{calc-embedded-preserve-modes}) command is given will be preserved when embedded mode is ended. @@ -31315,7 +31315,7 @@ on it in order to get it to notice the new annotation. Two more mode-recording modes selectable by @kbd{m R} are available which are also available outside of Embedded mode. -(@pxref{General Mode Commands}.) They are @code{Save}, in which mode +(@pxref{General Mode Commands}.) They are @code{Save}, in which mode settings are recorded permanently in your Calc init file (the file given by the variable @code{calc-settings-file}, typically @file{~/.emacs.d/calc.el}) rather than by annotating the current document, and no-recording @@ -35645,7 +35645,7 @@ formulas in normal language modes. If @code{calc-multiplication-has-precedence} is non-@code{nil}, then multiplication has precedence (and, for certain obscure reasons, is right associative), and so for example @samp{a/b*c} will be interpreted -as @samp{a/(b*c)}. If @code{calc-multiplication-has-precedence} is +as @samp{a/(b*c)}. If @code{calc-multiplication-has-precedence} is @code{nil}, then multiplication has the same precedence as division (and, like division, is left associative), and so for example @samp{a/b*c} will be interpreted as @samp{(a/b)*c}. The default value diff --git a/doc/misc/cc-mode.texi b/doc/misc/cc-mode.texi index ced59c0eee6..c0819b232a4 100644 --- a/doc/misc/cc-mode.texi +++ b/doc/misc/cc-mode.texi @@ -182,7 +182,7 @@ modify this GNU manual.'' @end quotation @end copying -@comment Info directory entry for use by install-info. The indentation +@comment Info directory entry for use by install-info. The indentation @comment here is by request from the FSF folks. @dircategory Emacs editing modes @direntry @@ -1429,7 +1429,7 @@ continuation of the preceding @code{if}. @findex abbrev-mode @cindex Abbrev mode @ccmode{} uses Abbrev mode (@pxref{Abbrevs,,,@emacsman{}, @emacsmantitle{}}) -to accomplish this. It's therefore turned on by default in all language +to accomplish this. It's therefore turned on by default in all language modes except IDL mode, since CORBA IDL doesn't have any statements. @end deffn @@ -2704,7 +2704,7 @@ for C code in GNU programs. @item k&r @cindex K&R style -The classic Kernighan and Ritchie style for C code. If you're looking +The classic Kernighan and Ritchie style for C code. If you're looking for the style used in the 2nd edition of their book ``The C Programming Language'', then check out the @code{stroustrup} style. @@ -7591,7 +7591,7 @@ Started}. @kindex C-M-\ @emph{How do I reindent the whole file?} -Visit the file and hit @kbd{C-x h} to mark the whole buffer. Then hit +Visit the file and hit @kbd{C-x h} to mark the whole buffer. Then hit @kbd{C-M-\}. @xref{Indentation Commands}. @item diff --git a/doc/misc/cl.texi b/doc/misc/cl.texi index c3a91f7dab1..113029700ec 100644 --- a/doc/misc/cl.texi +++ b/doc/misc/cl.texi @@ -860,7 +860,7 @@ Thus @code{(cl-typep @var{object} 'null)} is equivalent to @item The type symbol @code{atom} represents all objects that are not cons -cells. Thus @code{(cl-typep @var{object} 'atom)} is equivalent to +cells. Thus @code{(cl-typep @var{object} 'atom)} is equivalent to @code{(atom @var{object})}. @item @@ -2191,7 +2191,7 @@ term restricts the search to just the specified property. The Properties,,,elisp}. @item for @var{var} being the frames -This clause iterates over all Emacs frames. The clause @code{screens} is +This clause iterates over all Emacs frames. The clause @code{screens} is a synonym for @code{frames}. The frames are visited in @code{next-frame} order starting from @code{selected-frame}. diff --git a/doc/misc/dbus.texi b/doc/misc/dbus.texi index a98b738e73e..e2e9de729de 100644 --- a/doc/misc/dbus.texi +++ b/doc/misc/dbus.texi @@ -1255,7 +1255,7 @@ object. Example: @end lisp With the @code{dbus-introspect} function it is possible to explore the -interfaces of @samp{org.freedesktop.Hal} service. It offers the +interfaces of @samp{org.freedesktop.Hal} service. It offers the interfaces @samp{org.freedesktop.Hal.Manager} for the object at the path @samp{/org/freedesktop/Hal/Manager} as well as the interface @samp{org.freedesktop.Hal.Device} for all objects prefixed with the @@ -1970,7 +1970,7 @@ If this variable is non-@code{nil}, D-Bus specific debug messages are raised. Input parameters of @code{dbus-call-method}, @code{dbus-call-method-asynchronously}, @code{dbus-send-signal}, @code{dbus-register-method}, @code{dbus-register-property} and -@code{dbus-register-signal} are checked for correct D-Bus types. If +@code{dbus-register-signal} are checked for correct D-Bus types. If there is a type mismatch, the Lisp error @code{wrong-type-argument} @code{D-Bus @var{arg}} is raised. diff --git a/doc/misc/ebrowse.texi b/doc/misc/ebrowse.texi index dca6266d8ae..27a5deb86d9 100644 --- a/doc/misc/ebrowse.texi +++ b/doc/misc/ebrowse.texi @@ -513,8 +513,8 @@ practical than to clutter up the buffer list with dozens of member buffers. If you want to display more than one member list at a time you can -@dfn{freeze} its member buffer. Freezing a member buffer prevents it -from being overwritten the next time you display a member list. You can +@dfn{freeze} its member buffer. Freezing a member buffer prevents it +from being overwritten the next time you display a member list. You can toggle this buffer status at any time. Every member list display command in the tree buffer can be used with a @@ -747,7 +747,7 @@ menu. @cindex unmark all @item M a Unmark all classes. With prefix argument @kbd{C-u}, mark all classes in -the tree. Since this command operates on the whole buffer, it can also be +the tree. Since this command operates on the whole buffer, it can also be found in the buffer's object menu. @end table diff --git a/doc/misc/ede.texi b/doc/misc/ede.texi index ae179832753..4ed3fc9d1df 100644 --- a/doc/misc/ede.texi +++ b/doc/misc/ede.texi @@ -1120,7 +1120,7 @@ number. It also holds a list of @code{ede-target} objects and a list of sub projects, or more @code{ede-project} objects. New project types must subclass @code{ede-project} to add special -behavior. New project types also need to subclass @code{ede-target} to +behavior. New project types also need to subclass @code{ede-target} to add specialty behavior. In this way, the common @ede{} interface is designed to work against diff --git a/doc/misc/ediff.texi b/doc/misc/ediff.texi index 749025c870b..ae107323d9c 100644 --- a/doc/misc/ediff.texi +++ b/doc/misc/ediff.texi @@ -135,10 +135,10 @@ The architecture and the interface are, of course, drastically different. When Ediff starts up, it displays a small control window, which accepts the Ediff commands, and two or three windows displaying the files to be compared -or merged. The control window can be in its own small frame or it can be -part of a bigger frame that displays other buffers. In any case, it is +or merged. The control window can be in its own small frame or it can be +part of a bigger frame that displays other buffers. In any case, it is important that the control window be active (i.e., be the one receiving the -keystrokes) when you use Ediff. You can switch to other Emacs buffers at +keystrokes) when you use Ediff. You can switch to other Emacs buffers at will and even edit the files currently being compared with Ediff and then switch back to Ediff at any time by activating the appropriate Emacs windows. @@ -156,13 +156,13 @@ Compare two files. @item ediff-backup @findex ediff-backup -Compare a file with its backup. If there are several numerical backups, use -the latest. If the file is itself a backup, then compare it with its +Compare a file with its backup. If there are several numerical backups, use +the latest. If the file is itself a backup, then compare it with its original. @item ediff-current-file @findex ediff-current-file -Compare the buffer with its file on disk. This function can be used as a +Compare the buffer with its file on disk. This function can be used as a safe version of @code{revert-buffer}. @item ediff-buffers @@ -220,14 +220,14 @@ Compare text visible in 2 windows line-by-line. @findex ediff-regions-wordwise Compare regions word-by-word. The regions can come from the same buffer and they can even overlap. You will be asked to specify the buffers that -contain the regions, which you want to compare. For each buffer, you will -also be asked to mark the regions to be compared. Pay attention to the +contain the regions, which you want to compare. For each buffer, you will +also be asked to mark the regions to be compared. Pay attention to the messages that appear in the minibuffer. @item ediff-regions-linewise @findex ediff-regions-linewise Similar to @code{ediff-windows-linewise}, but compares the regions -line-by-line. See @code{ediff-windows-linewise} for more details. +line-by-line. See @code{ediff-windows-linewise} for more details. @item ediff-revision @findex ediff-revision @@ -246,7 +246,7 @@ will be able to patch the files selectively. @xref{Session Groups}, for more details. Since the patch might be in a buffer or a file, you will be asked which is -the case. To avoid this extra prompt, you can invoke this command with a +the case. To avoid this extra prompt, you can invoke this command with a prefix argument. With an odd prefix argument, Ediff assumes the patch is in a file; with an even argument, a buffer is assumed. @@ -280,7 +280,7 @@ This function would refuse to apply a multifile patch to a buffer. Use modified by the @code{patch} utility). Since the patch might be in a buffer or a file, you will be asked which is -the case. To avoid this extra prompt, you can invoke this command with a +the case. To avoid this extra prompt, you can invoke this command with a prefix argument. With an odd prefix argument, Ediff assumes the patch is in a file; with an even argument, a buffer is assumed. @@ -683,7 +683,7 @@ again puts Ediff back in the original state. @vindex ediff-ignore-case-option @vindex ediff-ignore-case-option3 @vindex ediff-ignore-case -Toggle case sensitivity in the diff program. All diffs are recomputed. +Toggle case sensitivity in the diff program. All diffs are recomputed. Case sensitivity is controlled by the variables @code{ediff-ignore-case-option}, @code{ediff-ignore-case-option3}, and @code{ediff-ignore-case}, which are explained elsewhere. @@ -814,7 +814,7 @@ it. Typing @kbd{$$} again undoes this setting. @kindex $* When merging files with large number of differences, it is sometimes convenient to be able to skip the difference regions for which you already -decided which variant is most appropriate. Typing @kbd{$*} will accomplish +decided which variant is most appropriate. Typing @kbd{$*} will accomplish precisely this. To be more precise, this toggles the check for whether the current merge is @@ -898,9 +898,9 @@ child Ediff session for comparing regions in buffers A, B, or C as follows. First, you will be asked whether you want to compare the fine differences -between the currently highlighted buffers on a word-by-word basis. If you +between the currently highlighted buffers on a word-by-word basis. If you accept, a child Ediff session will start using the currently highlighted -regions. Ediff will let you step over the differences word-wise. +regions. Ediff will let you step over the differences word-wise. If you reject the offer, you will be asked to select regions of your choice. @@ -1054,9 +1054,9 @@ directories. @cindex Directory difference buffer Sometimes it is desirable to copy some files from one directory to another -without exiting Ediff. The @emph{directory difference buffer}, which is +without exiting Ediff. The @emph{directory difference buffer}, which is displayed by typing @kbd{D} as discussed above, can be used for this -purpose. If a file is, say, in Ediff's Directory A, but is missing in +purpose. If a file is, say, in Ediff's Directory A, but is missing in Ediff's Directory B (Ediff will refuse to override existing files), then typing @kbd{C} or clicking mouse button 2 over that file (which must be displayed in directory difference buffer) will copy that file from @@ -1130,7 +1130,7 @@ for hiding or, with @kbd{=m}, for further operations. The comparison operations @kbd{==}, @kbd{=h}, and @kbd{=m} can recurse into subdirectories to see if they have identical contents (so the user will not -need to descend into those subdirectories manually). These commands ask the +need to descend into those subdirectories manually). These commands ask the user whether or not to do a recursive descent. @@ -1221,7 +1221,7 @@ of Ediff. @vindex ediff-after-setup-windows-hook These two hooks are called before and after Ediff sets up its window configuration. These hooks are run each time Ediff rearranges windows to -its liking. This happens whenever it detects that the user changed the +its liking. This happens whenever it detects that the user changed the windows setup. @item ediff-suspend-hook @@ -1323,7 +1323,7 @@ Hooks run after setting up the registry for all active Ediff session. @item ediff-before-session-group-setup-hook @vindex ediff-before-session-group-setup-hook Hooks run before setting up a control panel for a group of related Ediff -sessions. Can be used, for example, to save window configuration to restore +sessions. Can be used, for example, to save window configuration to restore later. @item ediff-after-session-group-setup-hook @vindex ediff-after-session-group-setup-hook @@ -1598,21 +1598,21 @@ problem. @vindex ediff-ignore-case-option @vindex ediff-ignore-case-option3 @vindex ediff-ignore-case -Finally, Ediff can be told to ignore the case of the letters. This behavior +Finally, Ediff can be told to ignore the case of the letters. This behavior can be toggled with @kbd{#c} and it is controlled with three variables: @code{ediff-ignore-case-option}, @code{ediff-ignore-case-option3}, and @code{ediff-ignore-case}. The variable @code{ediff-ignore-case-option} specifies the option to pass -to the diff program for comparing two files or buffers. For GNU -@code{diff}, this option is @code{"-i"}. The variable +to the diff program for comparing two files or buffers. For GNU +@code{diff}, this option is @code{"-i"}. The variable @code{ediff-ignore-case-option3} specifies the option to pass to the -@code{diff3} program in order to make it case-insensitive. GNU @code{diff3} +@code{diff3} program in order to make it case-insensitive. GNU @code{diff3} does not have such an option, so when merging or comparing three files with this program, ignoring the letter case is not supported. The variable @code{ediff-ignore-case} controls whether Ediff starts out by -ignoring letter case or not. It can be set in @file{.emacs} using +ignoring letter case or not. It can be set in @file{.emacs} using @code{setq-default}. When case sensitivity is toggled, all difference @@ -1875,11 +1875,11 @@ Customize interface instead of using @code{setq} directly.) @item ediff-coding-system-for-read @vindex ediff-coding-system-for-read This variable specifies the coding system to use when reading the output -that the programs @code{diff3} and @code{diff} send to Emacs. The default +that the programs @code{diff3} and @code{diff} send to Emacs. The default is @code{raw-text}, and this should work fine in Unix and in most -cases under Windows NT/98/2000. There are @code{diff} programs -for which the default option doesn't work under Windows. In such cases, -@code{raw-text-dos} might work. If not, you will have to experiment with +cases under Windows NT/98/2000. There are @code{diff} programs +for which the default option doesn't work under Windows. In such cases, +@code{raw-text-dos} might work. If not, you will have to experiment with other coding systems or use GNU diff. @item ediff-patch-program @@ -1992,7 +1992,7 @@ the difference region from the ancestor buffer, if available ======= end @end example -The above is the default template for the combined region. The user can +The above is the default template for the combined region. The user can customize this template using the variable @code{ediff-combination-pattern}. @@ -2000,11 +2000,11 @@ customize this template using the variable The variable @code{ediff-combination-pattern} specifies the template that determines how the combined merged region looks like. The template is represented as a list of the form @code{(STRING1 Symbol1 STRING2 Symbol2 -STRING3 Symbol3 STRING4)}. The symbols here must be atoms of the form -@code{A}, @code{B}, or @code{Ancestor}. They determine the order in which +STRING3 Symbol3 STRING4)}. The symbols here must be atoms of the form +@code{A}, @code{B}, or @code{Ancestor}. They determine the order in which the corresponding difference regions (from buffers A, B, and the ancestor buffer) are displayed in the merged region of buffer C@. The strings in the -template determine the text that separates the aforesaid regions. The +template determine the text that separates the aforesaid regions. The default template is @smallexample @@ -2014,8 +2014,8 @@ default template is @noindent (this is one long line) and the corresponding combined region is shown -above. The order in which the regions are shown (and the separator -strings) can be changed by changing the above template. It is even +above. The order in which the regions are shown (and the separator +strings) can be changed by changing the above template. It is even possible to add or delete region specifiers in this template (although the only possibly useful such modification seems to be the deletion of the ancestor). @@ -2154,7 +2154,7 @@ change this variable. @vindex ediff-merge-filename-prefix When merge buffers are saved automatically as directed by @code{ediff-autostore-merges}, Ediff attaches a prefix to each file, as -specified by the variable @code{ediff-merge-filename-prefix}. The default +specified by the variable @code{ediff-merge-filename-prefix}. The default is @code{merge_}, but this can be changed by the user. @node Support for Version Control @@ -2318,9 +2318,9 @@ unconditionally (e.g., by making @code{ediff-janitor} into one of these hooks). @item ediff-keep-tmp-versions @vindex ediff-keep-tmp-versions -Default is @code{nil}. If @code{t}, the versions of the files being +Default is @code{nil}. If @code{t}, the versions of the files being compared or merged using operations such as @code{ediff-revision} or -@code{ediff-merge-revisions} are not deleted on exit. The normal action is +@code{ediff-merge-revisions} are not deleted on exit. The normal action is to clean up and delete these version files. @item ediff-grab-mouse diff --git a/doc/misc/efaq-w32.texi b/doc/misc/efaq-w32.texi index c5ba6c8609f..411450cdc42 100644 --- a/doc/misc/efaq-w32.texi +++ b/doc/misc/efaq-w32.texi @@ -773,7 +773,7 @@ corrupted while unpacking and Emacs will not start. If it is still not working, send mail to the @email{help-gnu-emacs@@gnu.org} mailing list, describing what you've -done, and what you are seeing. (The more information you send the more +done, and what you are seeing. (The more information you send the more likely it is that you'll receive a helpful response.) @node Virus @@ -1592,7 +1592,7 @@ smtpmail is loaded, then you'll need to change @code{smtpmail-smtp-server}. If you are experiencing problems with sending large messages, check -the value of the variable @code{smtpmail-debug-info}. If it is +the value of the variable @code{smtpmail-debug-info}. If it is non-@code{nil}, you should set it to @code{nil}: @node Incoming mail with Rmail @@ -1908,9 +1908,9 @@ See the following two URLs for details: @cindex MSVC++, compiling within Emacs @findex compile -This is an app note on how to use Microsoft Visual C++ with Emacs. The +This is an app note on how to use Microsoft Visual C++ with Emacs. The experiments done below were done with Emacs 19.34.1 on Windows 95, -using Visual C++ 4.0 Standard Edition. Your mileage may vary. +using Visual C++ 4.0 Standard Edition. Your mileage may vary. This writeup assumes minimal knowledge of Emacs hacking on the part of the reader. @@ -1939,14 +1939,14 @@ For all versions of Windows you can alternatively set the variables just inside Emacs by using @code{setenv} calls in your init file. @xref{Installing Emacs,,Where do I put my init file?}. -You should now be able to compile from Emacs. Load a source file from -a VC++ project. Type @kbd{M-x compile}. Replace the proposed command line +You should now be able to compile from Emacs. Load a source file from +a VC++ project. Type @kbd{M-x compile}. Replace the proposed command line with: @example nmake -f @var{ProjectName}.mak @end example -You will find that this defaults to a debug build. You can change it +You will find that this defaults to a debug build. You can change it to a release build with: @example nmake -f @var{ProjectName}.mak CFG="@var{ProjectName} - Win32 Release" @@ -2018,21 +2018,21 @@ click on @code{Customize...}. In the @code{Tools} tab, click on @file{emacsclientw.exe} file in your Emacs bin directory, and select it. For arguments, use @option{+$(CurLine)} @option{"$(FilePath)"} and for the directory use the @code{$(WkspDir)} -(the quotes around FilePath handle paths with spaces in them). Set the -Menu Text to say "Em&acs". The @option{+$(CurLine)} will set point in -Emacs to the same line as the cursor position in VC++. The ampersand +(the quotes around FilePath handle paths with spaces in them). Set the +Menu Text to say "Em&acs". The @option{+$(CurLine)} will set point in +Emacs to the same line as the cursor position in VC++. The ampersand in the word @code{Em&acs} allows you to select emacs from the keyboard. (E is already used for the OLE control test container.) -You should now be able to go to any source file in your project. Then, -use the pull-down menu @code{Tools->Emacs}. The active file in your +You should now be able to go to any source file in your project. Then, +use the pull-down menu @code{Tools->Emacs}. The active file in your VC++ IDE should now be front and center in Emacs, all ready to edit as -you wish. If you use keystrokes to work the menus, try @kbd{Alt-T A} to -move the file into Emacs. Binding this tool to a keystroke will be +you wish. If you use keystrokes to work the menus, try @kbd{Alt-T A} to +move the file into Emacs. Binding this tool to a keystroke will be left as an exercise for the student. If you have the option of saving files before running tools, make sure -this option is set. (I don't see it on VC++ 4.0.) +this option is set. (I don't see it on VC++ 4.0.) @node Borland C++ Builder @section Emacs and Borland C++ Builder @@ -2072,8 +2072,8 @@ Free native Windows binaries. For those that don't Cygwin may be an option. From Jay Rogers: Some versions of the perl debugger itself need to be patched to work -with emacs. They are perl versions 5.001 and less, and version -5.004_01. To fix, locate and change the code similar to the following +with emacs. They are perl versions 5.001 and less, and version +5.004_01. To fix, locate and change the code similar to the following code in lib/perl5db.pl @example if (-e "/dev/tty") @{ @@ -2273,7 +2273,7 @@ If you have general questions about Emacs, the best places to start looking are @ref{Top,,, emacs, The GNU Emacs Manual}, and @ref{Top,,, efaq, the standard Emacs FAQ}. In Emacs, you can browse the manual using Info by typing @kbd{C-h r}, -and you can view the FAQ by typing @kbd{C-h C-f}. Other resources include: +and you can view the FAQ by typing @kbd{C-h C-f}. Other resources include: @itemize @item @uref{https://www.gnu.org/software/emacs/, The Emacs website} diff --git a/doc/misc/efaq.texi b/doc/misc/efaq.texi index f56888aac3f..fd98088bc7c 100644 --- a/doc/misc/efaq.texi +++ b/doc/misc/efaq.texi @@ -3693,7 +3693,7 @@ feature. Emacs has a list of local variables that are known to be safe to set. If a file tries to set any variable outside this list, it asks the -user to confirm whether the variables should be set. You can also tell +user to confirm whether the variables should be set. You can also tell Emacs whether to allow the evaluation of Emacs Lisp code found at the bottom of files by setting the variable @code{enable-local-eval}. @@ -3836,7 +3836,7 @@ in the distribution. To build Emacs from source for MS-DOS, see the instructions in the file @file{msdos/INSTALL} in the distribution. The DOS port builds and runs on plain DOS, and also on all versions of MS-Windows from version 3.X -onwards, including Windows XP and Vista. Pre-built binaries may be +onwards, including Windows XP and Vista. Pre-built binaries may be available at @uref{https://www.delorie.com/pub/djgpp/current/v2gnu/emacs.README} @@ -4762,14 +4762,14 @@ these systems, you should configure @code{movemail} to use @code{flock}. Ron Isaacson says: When you hit @kbd{r} to reply in Rmail, by default it Ccs all of the original recipients (everyone on the original @samp{To} and @samp{CC} -lists). With a prefix argument (i.e., typing @kbd{C-u} before @kbd{r}), +lists). With a prefix argument (i.e., typing @kbd{C-u} before @kbd{r}), it replies only to the sender. However, going through the whole @kbd{C-u} business every time you want to reply is a pain. This is the best fix I've been able to come up with: @lisp (defun rmail-reply-t () - "Reply only to the sender of the current message. (See rmail-reply.)" + "Reply only to the sender of the current message. (See rmail-reply.)" (interactive) (rmail-reply t)) diff --git a/doc/misc/eglot.texi b/doc/misc/eglot.texi index 85fef6be553..ba7aeb448e5 100644 --- a/doc/misc/eglot.texi +++ b/doc/misc/eglot.texi @@ -1313,7 +1313,7 @@ based on compile-time information. The language server reports the regions by periodically sending a @code{textDocument/inactiveRegions} notification for each managed -buffer (@pxref{Eglot and Buffers}). Normally, unknown server +buffer (@pxref{Eglot and Buffers}). Normally, unknown server notifications are ignored by Eglot, but we're going change that. Both the announcement of the client capability and the handling of the @@ -1353,7 +1353,7 @@ called @code{eglot-clangd}, so that the method would be simplified: However, this would require that users tweak @code{eglot-server-program} to tell Eglot instantiate such sub-classes instead of the generic @code{eglot-lsp-server} (@pxref{Setting Up LSP -Servers}). For the purposes of this particular demonstration, we're +Servers}). For the purposes of this particular demonstration, we're going to use the more hacky regexp route which doesn't require that. Note, however, that detecting server versions before announcing new diff --git a/doc/misc/emacs-mime.texi b/doc/misc/emacs-mime.texi index ef7ea614f8b..22bef4739a4 100644 --- a/doc/misc/emacs-mime.texi +++ b/doc/misc/emacs-mime.texi @@ -379,7 +379,7 @@ This variable is @code{resize} by default, which means that images that are bigger than the Emacs window are resized so that they fit. If you set this to @code{nil}, large images are not displayed in Emacs, but can instead be displayed externally (e.g., with -@samp{ImageMagick} or @samp{xv}). Setting this variable to @code{t} +@samp{ImageMagick} or @samp{xv}). Setting this variable to @code{t} disables this check and makes the library display all inline images as inline, regardless of their size. diff --git a/doc/misc/ert.texi b/doc/misc/ert.texi index cecde5f3232..109dbd0f0ce 100644 --- a/doc/misc/ert.texi +++ b/doc/misc/ert.texi @@ -203,11 +203,11 @@ different Emacs versions. @cindex interactive testing @findex ert -You can run the tests that are currently defined in your Emacs with -the command @kbd{M-x ert @key{RET} t @key{RET}}. (For an -explanation of the @code{t} argument, @pxref{Test Selectors}.) ERT will pop -up a new buffer, the ERT results buffer, showing the results of the -tests run. It looks like this: +You can run the tests that are currently defined in your Emacs with the +command @kbd{M-x ert @key{RET} t @key{RET}}. (For an explanation of the +@code{t} argument, @pxref{Test Selectors}.) ERT will pop up a new +buffer, the ERT results buffer, showing the results of the tests run. +It looks like this: @example Selector: t diff --git a/doc/misc/eshell.texi b/doc/misc/eshell.texi index fa410a89761..30825a497a9 100644 --- a/doc/misc/eshell.texi +++ b/doc/misc/eshell.texi @@ -329,7 +329,7 @@ form} or in @dfn{Lisp form}. You can use the semicolon (@code{;}) to separate multiple command invocations on a single line, executing each in turn. You can also -separate commands with @code{&&} or @code{||}. When using @code{&&}, +separate commands with @code{&&} or @code{||}. When using @code{&&}, Eshell will execute the second command only if the first succeeds (i.e.@: has an exit status of 0); with @code{||}, Eshell will execute the second command only if the first fails. @@ -1977,7 +1977,7 @@ Matches one or more copies of the glob pattern @var{x}. Thus, etc. @item @var{x}~@var{y} -Matches anything that matches the pattern @var{x} but not @var{y}. For +Matches anything that matches the pattern @var{x} but not @var{y}. For example, @samp{[[:digit:]]#~4?} matches @file{1} and @file{12}, but not @file{42}. Note that unlike in Zsh, only a single @samp{~} operator can be used in a pattern, and it cannot be inside of a group @@ -2398,9 +2398,9 @@ Adds the text passed to it to the clipboard. @findex eshell-close-target You can, of course, define your own virtual targets. These are entries in @code{eshell-virtual-targets} with the form @samp{(@var{filename} -@var{output-function} @var{pass-mode})}. The first element, +@var{output-function} @var{pass-mode})}. The first element, @var{filename}, is the device name, usually of the form -@samp{"/dev/@var{name}"}. The second, @var{output-function}, should be a +@samp{"/dev/@var{name}"}. The second, @var{output-function}, should be a function: Eshell will repeatedly call it with the redirected output. This argument can also be an @code{eshell-generic-target} instance. In this case, Eshell will repeatedly call the generic function @@ -2529,7 +2529,7 @@ for the built-in functions and some common external commands, and you can define your own for any command. @kindex TAB -Eshell completion also works for Lisp forms and glob patterns. If the +Eshell completion also works for Lisp forms and glob patterns. If the point is on a Lisp form, then @key{TAB} will behave similarly to completion in @code{elisp-mode} and @code{lisp-interaction-mode}. For glob patterns, the pattern will be removed from the input line, and @@ -2967,7 +2967,7 @@ Also a new @command{less} buffer was created with nothing in it@dots{} If @command{less.exe} is invoked from the Eshell command line, the expected output is written to the buffer. -Note that this happens on NT-Emacs 20.6.1 on Windows 2000. The term.el +Note that this happens on NT-Emacs 20.6.1 on Windows 2000. The term.el package and the supplied shell both use the @command{cmdproxy} program for running shells. diff --git a/doc/misc/eudc.texi b/doc/misc/eudc.texi index 615ab76c326..0a16f2561f7 100644 --- a/doc/misc/eudc.texi +++ b/doc/misc/eudc.texi @@ -131,7 +131,7 @@ Quoted from RFC 1777: @quotation [LDAP] is designed to provide access to the X.500 Directory while not incurring the resource requirements of the Directory Access Protocol -(DAP). This protocol is specifically targeted at simple management +(DAP). This protocol is specifically targeted at simple management applications and browser applications that provide simple read/write interactive access to the X.500 Directory, and is intended to be a complement to the DAP itself. @@ -564,7 +564,7 @@ to customize in this process. Before doing any query you will need to set the directory server. You need to specify the name of the host machine running the server software -and the protocol to use. If you do not set the server in any fashion, +and the protocol to use. If you do not set the server in any fashion, EUDC will ask you for one when you make your first query. You can set the server by selecting one from your hotlist of servers @@ -579,9 +579,9 @@ buffer will be displayed where you can edit the search base and other parameters for the server. @defvar eudc-server -The name or IP address of the remote directory server. A TCP port number +The name or IP address of the remote directory server. A TCP port number may be specified by appending a colon and a number to the name of the -server. You will not need this unless your server runs on a port other +server. You will not need this unless your server runs on a port other than the default (which depends on the protocol). If the directory server resides on your own computer (which is the case if you use the BBDB back end) then @samp{localhost} is a reasonable value but @@ -609,12 +609,12 @@ attributes you want to see, if different from the server defaults. @defvar eudc-default-return-attributes A list of the default attributes to extract from directory entries. If set to the symbol @code{all} then all available attributes are -returned. A value of @code{nil}, the default, means to return the +returned. A value of @code{nil}, the default, means to return the default attributes as configured in the server. @end defvar -The server may return several matching records to a query. Some of the -records may however not contain all the attributes you requested. You can +The server may return several matching records to a query. Some of the +records may however not contain all the attributes you requested. You can discard those records. @defopt eudc-strict-return-matches @@ -626,32 +626,32 @@ attributes are ignored. Default is @code{t}. @subsection Duplicate Attributes Directory standards may authorize different instances of the same -attribute in a record. For instance the record of a person may contain +attribute in a record. For instance the record of a person may contain several email fields containing different email addresses, in which case EUDC will consider the attribute duplicated. -EUDC has several methods to deal with duplicated attributes. The +EUDC has several methods to deal with duplicated attributes. The available methods are: @table @code @item list -Makes a list with the different values of the duplicate attribute. The +Makes a list with the different values of the duplicate attribute. The record is returned with only one instance of the attribute with a list -of all the different values as a value. This is the default method that +of all the different values as a value. This is the default method that is used to handle duplicate fields for which no other method has been specified. @item first Discards all the duplicate values of the field keeping only the first one. @item concat -Concatenates the different values using a newline as a separator. The +Concatenates the different values using a newline as a separator. The record keeps only one instance of the field the value of which is a single multi-line string. @item duplicate Duplicates the whole record into as many instances as there are different -values for the field. This is the default for the email field. Thus a +values for the field. This is the default for the email field. Thus a record containing 3 different email addresses is duplicated into three -different records each having a single email address. This is +different records each having a single email address. This is particularly useful in combination with @code{select} as the method to handle multiple matches in inline expansion queries (@pxref{Inline Query Expansion}) because you are presented with the 3 addresses in a @@ -667,7 +667,7 @@ A method to handle entries containing duplicate attributes. This is either an alist of elements @code{(@var{attr} . @var{method})}, or a symbol @var{method}. The alist form of the variable associates a method to an individual attribute name; the second form specifies a method applicable -to all attribute names. Available methods are: @code{list}, +to all attribute names. Available methods are: @code{list}, @code{first}, @code{concat}, and @code{duplicate} (see above). The default is @code{list}. @end defvar @@ -678,8 +678,8 @@ to all attribute names. Available methods are: @code{list}, @section Query Form The simplest way to query your directory server is to use the query -form. You display the query form with the @samp{Query with Form} menu -item or by invoking the command @kbd{M-x eudc-query-form}. The attribute +form. You display the query form with the @samp{Query with Form} menu +item or by invoking the command @kbd{M-x eudc-query-form}. The attribute names presented in this form are defined by the @code{eudc-query-form-attributes} variable (unless a non-@code{nil} argument is supplied to @code{eudc-query-form}). @@ -717,7 +717,7 @@ names for directory attribute names. This variable is ignored if @defvar eudc-user-attribute-names-alist This is an alist of user-defined names for the directory attributes used in -query/response forms. Prompt strings for attributes that are not in this +query/response forms. Prompt strings for attributes that are not in this alist are derived by splitting the attribute name at underscores and capitalizing the individual words. @end defvar @@ -893,7 +893,7 @@ against the @code{cn} attribute of LDAP servers: @defvar eudc-inline-expansion-format This variable lets you control exactly what is inserted into the -buffer upon an inline expansion request. It can be set to @code{nil}, +buffer upon an inline expansion request. It can be set to @code{nil}, to a function, or to a list. Default is @code{nil}. When the value is a list, the first element is a string passed to @@ -926,7 +926,7 @@ any of the formats: Email address specifications, as are generated by inline expansion, need to comply with RFC 5322 in order to be useful in email -messages. When an invalid address specification is present in an email +messages. When an invalid address specification is present in an email message header, the message is likely to be rejected by a receiving MTA. It is hence recommended to switch old configurations, which use a list value, to the new @code{nil}, or function value type since it diff --git a/doc/misc/flymake.texi b/doc/misc/flymake.texi index 6b605a6c095..af9639ebb5a 100644 --- a/doc/misc/flymake.texi +++ b/doc/misc/flymake.texi @@ -194,7 +194,7 @@ The following statuses are defined: @item [@var{nerrors} @var{nwarnings} ...] @tab Normal operation. @var{nerrors} and @var{nwarnings} are, respectively, the total number of errors and warnings found during the last buffer -check, for all backends. They may be followed by other totals for +check, for all backends. They may be followed by other totals for other types of diagnostics (@pxref{Flymake error types}). @item @code{Wait} diff --git a/doc/misc/forms.texi b/doc/misc/forms.texi index e0221d90fd9..226445ff9a0 100644 --- a/doc/misc/forms.texi +++ b/doc/misc/forms.texi @@ -298,9 +298,9 @@ Similar to @code{forms-next-field} but moves backwards. @item M-x forms-save-buffer @kindex C-x C-s @itemx C-x C-s -Forms mode replacement for @code{save-buffer}. When executed in the +Forms mode replacement for @code{save-buffer}. When executed in the forms buffer it will save the contents of the (modified) data buffer -instead. In Forms mode this function will be bound to @kbd{C-x C-s}. +instead. In Forms mode this function will be bound to @kbd{C-x C-s}. @findex forms-print @item M-x forms-print @@ -374,10 +374,10 @@ string @code{forms-field-sep}, which is @code{"\t"} (a Tab) by default. If the format of the data file is not suitable enough you can define the filter functions @code{forms-read-file-filter} and @code{forms-write-file-filter}. @code{forms-read-file-filter} is called -when the data file is read from disk into the data buffer. It operates -on the data buffer, ignoring read-only protections. When the data file +when the data file is read from disk into the data buffer. It operates +on the data buffer, ignoring read-only protections. When the data file is saved to disk @code{forms-write-file-filter} is called to cancel the -effects of @code{forms-read-file-filter}. After being saved, +effects of @code{forms-read-file-filter}. After being saved, @code{forms-read-file-filter} is called again to prepare the data buffer for further processing. @@ -488,7 +488,7 @@ The default value is @code{"\^k"}, the character Control-K@. Example: @findex forms-read-file-filter @item forms-read-file-filter This variable holds the name of a function to be called after the data -file has been read in. This can be used to transform the contents of the +file has been read in. This can be used to transform the contents of the data file into a format more suitable for forms processing. If it is @code{nil}, no function is called. For example, to maintain a gzipped database: @@ -533,7 +533,7 @@ modified, just before updating the Forms data file. If it is @findex forms-insert-after @item forms-insert-after If this variable is not @code{nil}, new records are created @emph{after} the -current record. Also, upon visiting a file, the initial position will be +current record. Also, upon visiting a file, the initial position will be at the last record instead of the first one. @findex forms-check-number-of-fields @@ -798,8 +798,8 @@ newline in a field, while @code{forms-multi-line} was @code{nil}. @item Field separator occurs in record - update refused! The current record contains the field separator string inside one of the -fields. It can not be written back to the data file, for it would -corrupt it. Probably you inserted the field separator string in a field. +fields. It can not be written back to the data file, for it would +corrupt it. Probably you inserted the field separator string in a field. @item Record number @var{xx} out of range 1..@var{yy} A jump was made to non-existing record @var{xx}. @var{yy} denotes the @@ -813,7 +813,7 @@ An attempt was made to enable edit mode on a file that has been write protected. @item Search failed: @var{regexp} -The @var{regexp} could not be found in the data file. Forward searching +The @var{regexp} could not be found in the data file. Forward searching is done from the current location until the end of the file, then retrying from the beginning of the file until the current location. Backward searching is done from the current location until the beginning @@ -828,7 +828,7 @@ Forms mode's idea of the number of records has been adjusted to the number of records actually present in the data file. @item Problem saving buffers? -An error occurred while saving the data file buffer. Most likely, Emacs +An error occurred while saving the data file buffer. Most likely, Emacs did ask to confirm deleting the buffer because it had been modified, and you said ``no''. @end table diff --git a/doc/misc/gnus-faq.texi b/doc/misc/gnus-faq.texi index 33c9f3bea81..a773d48417c 100644 --- a/doc/misc/gnus-faq.texi +++ b/doc/misc/gnus-faq.texi @@ -115,7 +115,7 @@ development version that became Gnus 5.12. * FAQ 2-4:: My group buffer becomes a bit crowded, is there a way to sort my groups into categories so I can easier browse through them? -* FAQ 2-5:: How to manually sort the groups in Group buffer? How to +* FAQ 2-5:: How to manually sort the groups in Group buffer? How to sort the groups in a topic? @end menu @@ -146,7 +146,7 @@ what's this? @subsubheading Answer You get the message described in the q/a pair above while -starting Gnus, right? It's another symptom for the same +starting Gnus, right? It's another symptom for the same problem, so read the answer above. @node FAQ 2-3 @@ -190,7 +190,7 @@ groups nicely indented. @node FAQ 2-5 @subsubheading Question 2.5 -How to manually sort the groups in Group buffer? How to +How to manually sort the groups in Group buffer? How to sort the groups in a topic? @subsubheading Answer @@ -583,7 +583,7 @@ each POP3 mail source. @xref{Mail Source Specifiers}, for details on * FAQ 4-8:: Is there anything I can do to make poorly formatted mails more readable? * FAQ 4-9:: Is there a way to automatically ignore posts by specific - authors or with specific words in the subject? And can I + authors or with specific words in the subject? And can I highlight more interesting ones in some way? * FAQ 4-10:: How can I disable threading in some (e.g., mail-) groups, or set other variables specific for some groups? @@ -593,7 +593,7 @@ each POP3 mail source. @xref{Mail Source Specifiers}, for details on displays in group buffer is by far to high, especially in mail groups. Is this a bug? * FAQ 4-13:: I don't like the layout of summary and article buffer, - how to change it? Perhaps even a three pane display? + how to change it? Perhaps even a three pane display? * FAQ 4-14:: I don't like the way the Summary buffer looks, how to tweak it? * FAQ 4-15:: How to split incoming mails in several groups? @@ -750,7 +750,7 @@ other deuglifications). @subsubheading Question 4.9 Is there a way to automatically ignore posts by specific -authors or with specific words in the subject? And can I +authors or with specific words in the subject? And can I highlight more interesting ones in some way? @subsubheading Answer @@ -876,7 +876,7 @@ groups again). @subsubheading Question 4.13 I don't like the layout of summary and article buffer, how -to change it? Perhaps even a three pane display? +to change it? Perhaps even a three pane display? @subsubheading Answer @@ -1056,7 +1056,7 @@ of the variables @code{shr-color-visible-distance-min} and signature...? * FAQ 5-4:: Can I set things like From, Signature etc. group based on the group I post too? -* FAQ 5-5:: Is there a spell-checker? Perhaps even on-the-fly +* FAQ 5-5:: Is there a spell-checker? Perhaps even on-the-fly spell-checking? * FAQ 5-6:: Can I set the dictionary based on the group I'm posting to? @@ -1212,7 +1212,7 @@ at the bottom. @node FAQ 5-5 @subsubheading Question 5.5 -Is there a spell-checker? Perhaps even on-the-fly spell-checking? +Is there a spell-checker? Perhaps even on-the-fly spell-checking? @subsubheading Answer @@ -1562,7 +1562,7 @@ gnu.emacs.gnus and want to archive it there are several solutions. The first and easiest is to save it to a file by saying @kbd{O f}. However, wouldn't it be much more convenient to have more direct access to -the archived message from Gnus? If you say yes, put this +the archived message from Gnus? If you say yes, put this snippet by Frank Haun in @file{~/.gnus.el}: @@ -1584,7 +1584,7 @@ more then one article." @noindent You can now say @kbd{M-x my-archive-article} in summary buffer to -archive the article under the cursor in a nnml group. (Change nnml to +archive the article under the cursor in a nnml group. (Change nnml to your preferred back end.) Of course you can also make sure the cache is enabled by saying @@ -1664,7 +1664,7 @@ follows a slightly different approach, here all article where the read mark is set are expirable. To activate auto-expire, include auto-expire in the -Group parameters for the group. (Hit @kbd{G +Group parameters for the group. (Hit @kbd{G c} in summary buffer with point over the group to change group parameters). For total-expire add total-expire to the group-parameters. @@ -1808,7 +1808,7 @@ other possibility is to set, again in the summary buffer, downloadable (%) marks for the articles you want by typing @kbd{@@} with point over the article and then typing @kbd{J u}. -What's the difference? Well, process marks are erased as +What's the difference? Well, process marks are erased as soon as you exit the summary buffer while downloadable marks are permanent. You can actually set downloadable marks in several groups then use fetch session ('J s' in diff --git a/doc/misc/gnus.texi b/doc/misc/gnus.texi index d0ede930996..f4c87bd64dd 100644 --- a/doc/misc/gnus.texi +++ b/doc/misc/gnus.texi @@ -5837,7 +5837,7 @@ Mail a very wide reply to the author of the current article (@code{gnus-summary-very-wide-reply}). A @dfn{very wide reply} is a reply that goes out to all people listed in the @code{To}, @code{From} (or @code{Reply-To}) and @code{Cc} headers in all the process/prefixed -articles. This command uses the process/prefix convention. If given a +articles. This command uses the process/prefix convention. If given a prefix argument, the body of the current article will also be yanked. @item S V @@ -7424,7 +7424,7 @@ meaningful. Here's one example: @end lisp And another example: the protonmail bridge adds fake message-ids to -@code{References} in message headers, which can confuse threading. To +@code{References} in message headers, which can confuse threading. To remove these spurious ids @lisp @@ -10558,7 +10558,7 @@ course, it'll make group entry somewhat slow. @vindex gnus-refer-thread-use-search If @code{gnus-refer-thread-use-search} is @code{nil} (the default) -then thread-referral only looks for articles in the current group. If +then thread-referral only looks for articles in the current group. If this variable is @code{t} the server to which the current group belongs is searched (provided that searching is available for the server's backend). If this variable is a list of servers, each server @@ -14706,7 +14706,7 @@ Here's a complete example @code{nnimap} backend with a client-side If you're using Google's Gmail, you may want to see your Gmail labels when reading your mail. Gnus can give you this information if you ask -for @samp{X-GM-LABELS} in the variable @code{gnus-extra-headers}. For +for @samp{X-GM-LABELS} in the variable @code{gnus-extra-headers}. For example: @example @@ -15387,7 +15387,7 @@ corresponding keywords. @item :mailbox The name of the mailbox to get mail from. The default is @samp{INBOX} -which normally is the mailbox which receives incoming mail. Instead of +which normally is the mailbox which receives incoming mail. Instead of a single mailbox, this can be a list of mailboxes to fetch mail from. @item :predicate @@ -20602,7 +20602,7 @@ key will lead to creation of @file{ADAPT} files.) @cindex score file atoms @item score-fn The value of this entry should be one or more user-defined function -names in parentheses. Each function will be called in order and the +names in parentheses. Each function will be called in order and the returned value is required to be an integer. @example @@ -22355,7 +22355,7 @@ calling @code{nnmairix-search} with @samp{f:From}. @item G G o @kindex G G o @r{(Summary)} @findex nnmairix-goto-original-article -(Only in @code{nnmairix} groups!) Tries determine the group this article +(Only in @code{nnmairix} groups!) Tries determine the group this article originally came from and displays the article in this group, so that, e.g., replying to this article the correct posting styles/group parameters are applied (@code{nnmairix-goto-original-article}). This @@ -26641,13 +26641,13 @@ data across multiple machines. Very often, you want all your marks (what articles you've read, which ones were important, and so on) to be synchronized between several -machines. With IMAP, that's built into the protocol, so you can read +machines. With IMAP, that's built into the protocol, so you can read nnimap groups from many machines and they are automatically -synchronized. But NNTP, nnrss, and many other backends do not store +synchronized. But NNTP, nnrss, and many other backends do not store marks, so you have to do it locally. The Gnus Cloud package stores the marks, plus any files you choose, on -an IMAP server in a special folder. It's like a +an IMAP server in a special folder. It's like a DropTorrentSyncBoxOakTree(TM).@footnote{The name ``Gnus Cloud'' parodizes but otherwise has little to do with ``cloud computing'', a @url{https://www.gnu.org/philosophy/words-to-avoid.html#CloudComputing, @@ -26661,17 +26661,17 @@ misleading term normally best avoided}.} @node Gnus Cloud Setup @subsection Gnus Cloud Setup -Setting up the Gnus Cloud takes less than a minute. From the Group +Setting up the Gnus Cloud takes less than a minute. From the Group buffer: -Press @kbd{^} to go to the Server buffer. Here you'll see all the +Press @kbd{^} to go to the Server buffer. Here you'll see all the servers that Gnus knows. @xref{Server Buffer}. Then press @kbd{i} to mark any servers as cloud-synchronized (their marks are synchronized). Then press @kbd{I} to mark a single server as the cloud host (it must be an IMAP server, and will host a special IMAP folder with all the -synchronization data). This will set the variable +synchronization data). This will set the variable @code{gnus-cloud-method} (using the Customize facilities), then ask you to optionally upload your first CloudSynchronizationDataPack(TM). @@ -26691,37 +26691,37 @@ Download the latest Gnus Cloud data. @item ~ ~ @findex gnus-cloud-upload-all-data @cindex cloud, download -Upload the local Gnus Cloud data. Creates a new +Upload the local Gnus Cloud data. Creates a new CloudSynchronizationDataPack(TM). @end table -But wait, there's more. Of course there's more. So much more. You can +But wait, there's more. Of course there's more. So much more. You can customize all of the following. @defvar gnus-cloud-synced-files These are the files that will be part of every -CloudSynchronizationDataPack(TM). They are included in every upload, -so don't synchronize a lot of large files. Files under 100Kb are best. +CloudSynchronizationDataPack(TM). They are included in every upload, +so don't synchronize a lot of large files. Files under 100Kb are best. @end defvar @defvar gnus-cloud-storage-method -This is a choice from several storage methods. It's highly recommended -to use the EPG facilities. It will be automatic if have GnuPG -installed and EPG loaded. Otherwise, you could use Base64+gzip, +This is a choice from several storage methods. It's highly recommended +to use the EPG facilities. It will be automatic if have GnuPG +installed and EPG loaded. Otherwise, you could use Base64+gzip, Base64, or no encoding. @end defvar @defvar gnus-cloud-interactive When this is set, and by default it is, the Gnus Cloud package will -ask you for confirmation here and there. Leave it on until you're +ask you for confirmation here and there. Leave it on until you're comfortable with the package. @end defvar @defvar gnus-cloud-method The name of the IMAP server to store the -CloudSynchronizationDataPack(TM)s. It's easiest to set this from the +CloudSynchronizationDataPack(TM)s. It's easiest to set this from the Server buffer (@pxref{Gnus Cloud Setup}). @end defvar diff --git a/doc/misc/htmlfontify.texi b/doc/misc/htmlfontify.texi index 7446f3ee9f4..40d5d13b51f 100644 --- a/doc/misc/htmlfontify.texi +++ b/doc/misc/htmlfontify.texi @@ -1167,7 +1167,7 @@ An assoc of @code{(point . @var{face-symbol})} or . end)} elements, in descending order of point value (i.e., from the file's end to its beginning). The map is in reverse order because inserting a @samp{