procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

; Improve wording in documentation of 'not and 'null'

Browse source 
* doc/lispref/control.texi (Combining Conditions):
* doc/lispref/lists.texi (List-related Predicates): Clarify
wording of 'not' vs 'null'.  (Bug#70392)
This commit is contained in:
Eli Zaretskii 2024-04-15 14:52:03 +03:00
parent 5971aa1fd3
commit ecb80e0e8a
2 changed files with 5 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
doc/lispref/control.texi
View file

@ -349,7 +349,8 @@ kinds of multiple conditional constructs.
This function tests for the falsehood of @var{condition}. It returns
@code{t} if @var{condition} is @code{nil}, and @code{nil} otherwise.
The function @code{not} is identical to @code{null}, and we recommend
using the name @code{null} if you are testing for an empty list.
using the name @code{null} if you are testing for an empty list or
@code{nil} value.
@end defun
@defspec and conditions@dots{}

6
doc/lispref/lists.texi
View file

@ -143,9 +143,9 @@ This function is the opposite of @code{listp}: it returns @code{t} if
@defun null object
This function returns @code{t} if @var{object} is @code{nil}, and
returns @code{nil} otherwise. This function is identical to @code{not},
but as a matter of clarity we use @code{null} when @var{object} is
considered a list and @code{not} when it is considered a truth value
(see @code{not} in @ref{Combining Conditions}).
but as a matter of clarity we use @code{not} when @var{object} is
considered a truth value (see @code{not} in @ref{Combining
Conditions}) and @code{null} otherwise.
@example
@group