summaryrefslogtreecommitdiff
path: root/lisp/emacs-lisp/checkdoc.el
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2015-05-21 10:04:45 -0700
committerPaul Eggert <eggert@cs.ucla.edu>2015-05-21 10:06:44 -0700
commit96794d2f97cd064e4c2bf4f71459b42558cc8c79 (patch)
treeae2d3836af726636586f4ed21dbdfcb079715777 /lisp/emacs-lisp/checkdoc.el
parentfc071bf7c6a300f52142b92cf99c5a0e63b3e235 (diff)
downloademacs-96794d2f97cd064e4c2bf4f71459b42558cc8c79.tar.gz
emacs-96794d2f97cd064e4c2bf4f71459b42558cc8c79.tar.bz2
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/emacs-lisp/checkdoc.el')
-rw-r--r--lisp/emacs-lisp/checkdoc.el4
1 files changed, 2 insertions, 2 deletions
diff --git a/lisp/emacs-lisp/checkdoc.el b/lisp/emacs-lisp/checkdoc.el
index fc257d0d520..18361c8888f 100644
--- a/lisp/emacs-lisp/checkdoc.el
+++ b/lisp/emacs-lisp/checkdoc.el
@@ -1615,8 +1615,8 @@ function,command,variable,option or symbol." ms1))))))
(or
;; * The documentation string for a variable that is a
;; yes-or-no flag should start with words such as Non-nil
- ;; means..., to make it clear that all non-`nil' values are
- ;; equivalent and indicate explicitly what `nil' and non-`nil'
+ ;; means..., to make it clear that all non-nil values are
+ ;; equivalent and indicate explicitly what nil and non-nil
;; mean.
;; * If a user option variable records a true-or-false
;; condition, give it a name that ends in `-flag'.