"(list (read-char-by-name \"Insert character: \")\
(prefix-numeric-value current-prefix-arg)\
t))",
- doc: /* @dots{} /*)
+ doc: /* @dots{} */)
@end group
@end example
@example
@group
DEFUN ("bar", Fbar, Sbar, 0, UNEVALLED, 0
- doc: /* @dots{} /*
+ doc: /* @dots{} */
attributes: @var{attr1} @var{attr2} @dots{})
@end group
@end example
@example
(interactive (list (or current-prefix-arg 'toggle)))
-(let ((enable (if (eq arg 'toggle)
- (not foo-mode) ; @r{this mode's mode variable}
- (> (prefix-numeric-value arg) 0))))
+(let ((enable
+ (if (eq arg 'toggle)
+ (not foo-mode) ; @r{this is the mode's mode variable}
+ (> (prefix-numeric-value arg) 0))))
(if enable
@var{do-enable}
@var{do-disable}))
The @code{font-lock-multiline} property is meant to ensure proper
refontification; it does not automatically identify new multiline
-constructs. Identifying the requires that Font Lock mode operate on
+constructs. Identifying them requires that Font Lock mode operate on
large enough chunks at a time. This will happen by accident on many
cases, which may give the impression that multiline constructs magically
work. If you set the @code{font-lock-multiline} variable
the function is called. This is the window-relative horizontal
coordinate of point, measured in units of font width of the frame's
default face. Providing it speeds up the function, especially in very
-long lines, because it doesn't have to go back in the buffer in order
-to determine the current column. Note that @var{cur-col} is also
-counted from the visual start of the line.
+long lines, because the function doesn't have to go back in the buffer
+in order to determine the current column. Note that @var{cur-col} is
+also counted from the visual start of the line.
@end defun
@defun count-screen-lines &optional beg end count-final-newline window
@result{} t
@end group
@group
-(seq-some #'numberp [2 4 "6"])
+(seq-every-p #'numberp [2 4 "6"])
@result{} nil
@end group
@end example
@end group
@group
(seq-uniq '(1 2 2.0 1.0) #'=)
-@result{} [1 2]
+@result{} (1 2)
@end group
@end example
@end defun
The argument @var{how}, if non-@code{nil} specifies explicitly the style
of justification. It can be @code{left}, @code{right}, @code{full},
-@code{center}, or @code{none}. If it is @code{t}, that means to do
+@code{center}, or @code{none}. If it is @code{t}, that means to
follow specified justification style (see @code{current-justification},
below). @code{nil} means to do full justification.
those face(s) are retained. This function sets the @code{face}
property to a list of faces, with @var{face} as the first element (by
default) and the pre-existing faces as the remaining elements. If the
-optional argument @var{append} is non-@code{nil}, @var{face} is
+optional argument @var{appendp} is non-@code{nil}, @var{face} is
appended to the end of the list instead. Note that in a face list,
the first occurring value for each attribute takes precedence.
This function can be used to transpose stretches of text:
@defun transpose-regions start1 end1 start2 end2 &optional leave-markers
-This function exchanges two nonoverlapping portions of the buffer.
-Arguments @var{start1} and @var{end1} specify the bounds of one portion
-and arguments @var{start2} and @var{end2} specify the bounds of the
-other portion.
+This function exchanges two nonoverlapping portions of the buffer (if
+they overlap, the function signals an error). Arguments @var{start1}
+and @var{end1} specify the bounds of one portion and arguments
+@var{start2} and @var{end2} specify the bounds of the other portion.
Normally, @code{transpose-regions} relocates markers with the transposed
text; a marker previously positioned within one of the two transposed
elsewhere in the program.
@item
-Otherwise, define the variable with @code{defvar}, @code{defconst}, or
-@code{defcustom}. @xref{Defining Variables}. Usually, the definition
-should be at top-level in an Emacs Lisp file. As far as possible, it
-should include a documentation string which explains the meaning and
-purpose of the variable. You should also choose the variable's name
-to avoid name conflicts (@pxref{Coding Conventions}).
+Otherwise, define the variable with @code{defvar}, @code{defconst}
+(@pxref{Defining Variables}), or @code{defcustom} (@pxref{Variable
+Definitions}). Usually, the definition should be at top-level in an
+Emacs Lisp file. As far as possible, it should include a
+documentation string which explains the meaning and purpose of the
+variable. You should also choose the variable's name to avoid name
+conflicts (@pxref{Coding Conventions}).
Then you can bind the variable anywhere in a program, knowing reliably
what the effect will be. Wherever you encounter the variable, it will
@group
(defun search-for-abc ()
"Search for the string \"abc\", ignoring case differences."
- (let ((case-fold-search nil))
+ (let ((case-fold-search t))
(re-search-forward "abc")))
@end group
@end example
If @var{window} is part of a horizontal combination and the value of the
option @code{fit-window-to-buffer-horizontally} (see below) is
-non-@code{nil}, this function adjusts @var{window}'s height. The new
+non-@code{nil}, this function adjusts @var{window}'s width. The new
width of @var{window} is calculated from the maximum length of its
buffer's lines that follow the current start position of @var{window}.
The optional argument @var{max-width} specifies a maximum width and
projects / emacs.git / commitdiff