aboutsummaryrefslogtreecommitdiffstats
path: root/lisp/eshell
diff options
context:
space:
mode:
authorPaul Eggert2015-05-21 10:04:45 -0700
committerPaul Eggert2015-05-21 10:06:44 -0700
commit96794d2f97cd064e4c2bf4f71459b42558cc8c79 (patch)
treeae2d3836af726636586f4ed21dbdfcb079715777 /lisp/eshell
parentfc071bf7c6a300f52142b92cf99c5a0e63b3e235 (diff)
downloademacs-96794d2f97cd064e4c2bf4f71459b42558cc8c79.tar.gz
emacs-96794d2f97cd064e4c2bf4f71459b42558cc8c79.zip
Don't quote nil and t in doc strings
This is as per "Tips for Documentation Strings" in the elisp manual. For consistency, do the same in diagnostics and comments.
Diffstat (limited to 'lisp/eshell')
-rw-r--r--lisp/eshell/esh-mode.el2
-rw-r--r--lisp/eshell/esh-util.el2
2 files changed, 2 insertions, 2 deletions
diff --git a/lisp/eshell/esh-mode.el b/lisp/eshell/esh-mode.el
index 222e801301b..0dac4780690 100644
--- a/lisp/eshell/esh-mode.el
+++ b/lisp/eshell/esh-mode.el
@@ -206,7 +206,7 @@ This is used by `eshell-watch-for-password-prompt'."
206 206
207;; Internal Variables: 207;; Internal Variables:
208 208
209;; these are only set to `nil' initially for the sake of the 209;; these are only set to nil initially for the sake of the
210;; byte-compiler, when compiling other files which `require' this one 210;; byte-compiler, when compiling other files which `require' this one
211(defvar eshell-mode nil) 211(defvar eshell-mode nil)
212(defvar eshell-mode-map nil) 212(defvar eshell-mode-map nil)
diff --git a/lisp/eshell/esh-util.el b/lisp/eshell/esh-util.el
index 697f97e0460..170779fc5cd 100644
--- a/lisp/eshell/esh-util.el
+++ b/lisp/eshell/esh-util.el
@@ -33,7 +33,7 @@
33;;; User Variables: 33;;; User Variables:
34 34
35(defcustom eshell-stringify-t t 35(defcustom eshell-stringify-t t
36 "If non-nil, the string representation of t is 't'. 36 "If non-nil, the string representation of t is \"t\".
37If nil, t will be represented only in the exit code of the function, 37If nil, t will be represented only in the exit code of the function,
38and not printed as a string. This causes Lisp functions to behave 38and not printed as a string. This causes Lisp functions to behave
39similarly to external commands, as far as successful result output." 39similarly to external commands, as far as successful result output."