; bug#39779: Fix some typos in documentation.
This commit is contained in:
parent
696ee02c3a
commit
ff729e3f97
7 changed files with 12 additions and 12 deletions
|
@ -3260,7 +3260,7 @@ that deletion fails for whatever reason, the child frame is made a
|
|||
top-level frame.
|
||||
|
||||
Whether a child frame can have a menu or tool bar is window-system or
|
||||
window manager dependent. Most window-systems explicitly disallow menus
|
||||
window manager dependent. Most window-systems explicitly disallow menu
|
||||
bars for child frames. It seems advisable to disable both, menu and
|
||||
tool bars, via the frame's initial parameters settings.
|
||||
|
||||
|
|
|
@ -1076,7 +1076,7 @@ package is only activated if all its dependencies have been).
|
|||
Its format is a list of lists on a single line. The @code{car} of
|
||||
each sub-list is the name of a package, as a symbol. The @code{cadr}
|
||||
of each sub-list is the minimum acceptable version number, as a string
|
||||
that can be parse by @code{version-to-list}. An entry that lacks a
|
||||
that can be parsed by @code{version-to-list}. An entry that lacks a
|
||||
version (i.e., an entry which is just a symbol, or a sub-list of one
|
||||
element) is equivalent to entry with version "0". For instance:
|
||||
|
||||
|
|
|
@ -858,7 +858,7 @@ is a buffer if the buffer-local value of the variable is being
|
|||
changed, @code{nil} otherwise.
|
||||
@end defun
|
||||
|
||||
@defun remove-variable-watch symbol watch-function
|
||||
@defun remove-variable-watcher symbol watch-function
|
||||
This function removes @var{watch-function} from @var{symbol}'s list of
|
||||
watchers.
|
||||
@end defun
|
||||
|
|
|
@ -3187,7 +3187,7 @@ For example:
|
|||
(broken-reply-to . t))))
|
||||
@end lisp
|
||||
|
||||
All clauses that matches the group name will be used, but the last
|
||||
All clauses that match the group name will be used, but the last
|
||||
setting ``wins''. So if you have two clauses that both match the
|
||||
group name, and both set, say @code{display}, the last setting will
|
||||
override the first.
|
||||
|
@ -17880,7 +17880,7 @@ presence of 7 special headers. These headers are of the form
|
|||
@code{X-Diary-<something>}, @code{<something>} being one of
|
||||
@code{Minute}, @code{Hour}, @code{Dom}, @code{Month}, @code{Year},
|
||||
@code{Time-Zone} and @code{Dow}. @code{Dom} means ``Day of Month'', and
|
||||
@code{dow} means ``Day of Week''. These headers actually behave like
|
||||
@code{Dow} means ``Day of Week''. These headers actually behave like
|
||||
crontab specifications and define the event date(s):
|
||||
|
||||
@itemize @bullet
|
||||
|
@ -30922,7 +30922,7 @@ description = <string>
|
|||
|
||||
Believe it or not, but some people who use Gnus haven't really used
|
||||
Emacs much before they embarked on their journey on the Gnus Love Boat.
|
||||
If you are one of those unfortunates whom ``@kbd{C-M-a}'', ``kill the
|
||||
If you are one of those unfortunates to whom ``@kbd{C-M-a}'', ``kill the
|
||||
region'', and ``set @code{gnus-flargblossen} to an alist where the key
|
||||
is a regexp that is used for matching on the group name'' are magical
|
||||
phrases with little or no meaning, then this appendix is for you. If
|
||||
|
|
|
@ -739,9 +739,9 @@ stepping, you will see where the loop starts and ends. Also, examine
|
|||
the data being used in the loop and try to determine why the loop does
|
||||
not exit when it should.
|
||||
|
||||
On GNU and Unix systems, you can also trying sending Emacs SIGUSR2,
|
||||
On GNU and Unix systems, you can also try sending Emacs SIGUSR2,
|
||||
which, if 'debug-on-event' has its default value, will cause Emacs to
|
||||
attempt to break it out of its current loop and into the Lisp
|
||||
attempt to break out of its current loop and enter the Lisp
|
||||
debugger. (See the node "Debugging" in the ELisp manual for the
|
||||
details about the Lisp debugger.) This feature is useful when a
|
||||
C-level debugger is not conveniently available.
|
||||
|
|
|
@ -7774,11 +7774,11 @@ also be Lisp expression evaluating to a string),
|
|||
BUTTON: is the number of the regexp grouping actually matching the button,
|
||||
FORM: is a Lisp expression which must eval to true for the button to
|
||||
be added,
|
||||
CALLBACK: is the function to call when the user push this button, and each
|
||||
CALLBACK: is the function to call when the user pushes this button, and each
|
||||
PAR: is a number of a regexp grouping whose text will be passed to CALLBACK.
|
||||
|
||||
CALLBACK can also be a variable, in that case the value of that
|
||||
variable it the real callback function."
|
||||
CALLBACK can also be a variable, in which case the value of that
|
||||
variable is the real callback function."
|
||||
:group 'gnus-article-buttons
|
||||
:type '(repeat (list (choice regexp variable sexp)
|
||||
(integer :tag "Button")
|
||||
|
|
|
@ -174,7 +174,7 @@ no effect when spam-stat is invoked through spam.el."
|
|||
|
||||
(defcustom spam-stat-score-buffer-user-functions nil
|
||||
"List of additional scoring functions.
|
||||
Called one by one on the buffer.
|
||||
Called one by one on the buffer.
|
||||
|
||||
If all of these functions return non-nil answers, these numerical
|
||||
answers are added to the computed spam stat score on the buffer. If
|
||||
|
|
Loading…
Add table
Reference in a new issue