diff options
| author | Richard M. Stallman <rms@gnu.org> | 2006-05-02 00:09:03 +0000 |
|---|---|---|
| committer | Richard M. Stallman <rms@gnu.org> | 2006-05-02 00:09:03 +0000 |
| commit | d0789de9cd31b775d4e7933fbe99089d1a0144d2 (patch) | |
| tree | 3a848ad0c5d8d47b186516434a9b6552e991758c /lispref/intro.texi | |
| parent | beea1ef6c5f76c289f0e42130d4221f7bde7ec4b (diff) | |
| download | emacs-d0789de9cd31b775d4e7933fbe99089d1a0144d2.tar.gz | |
(nil and t): Clarify.
Diffstat (limited to 'lispref/intro.texi')
| -rw-r--r-- | lispref/intro.texi | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/lispref/intro.texi b/lispref/intro.texi index 61dfca64b97..7e1b6155b35 100644 --- a/lispref/intro.texi +++ b/lispref/intro.texi @@ -163,7 +163,7 @@ person reading this manual, are thought of as ``the programmer'' and are addressed as ``you''. ``The user'' is the person who uses Lisp programs, including those you write. -@cindex fonts +@cindex fonts in this manual Examples of Lisp code are formatted like this: @code{(list 1 2 3)}. Names that represent metasyntactic variables, or arguments to a function being described, are formatted like this: @var{first-number}. @@ -187,14 +187,14 @@ readers. After the Lisp reader has read either @samp{()} or @samp{nil}, there is no way to determine which representation was actually written by the programmer. - In this manual, we use @code{()} when we wish to emphasize that it -means the empty list, and we use @code{nil} when we wish to emphasize + In this manual, we write @code{()} when we wish to emphasize that it +means the empty list, and we write @code{nil} when we wish to emphasize that it means the truth value @var{false}. That is a good convention to use in Lisp programs also. @example (cons 'foo ()) ; @r{Emphasize the empty list} -(not nil) ; @r{Emphasize the truth value @var{false}} +(setq foo-flag nil) ; @r{Emphasize the truth value @var{false}} @end example @cindex @code{t}, uses of |