From: Eli Zaretskii <eliz@gnu.org>
Date: Sun, 13 Oct 2019 07:59:18 +0000 (+0300)
Subject: ; Minor copyedits in a recent ELisp manual change.
X-Git-Tag: emacs-27.0.90~1107
X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=f113ae59222dbb0961a34c1e0913cf0f3104a567;p=emacs.git

; Minor copyedits in a recent ELisp manual change.

* doc/lispref/tips.texi (Coding Conventions): Make the
guideline against '-p' in variable names less mandatory and
more constructive.
---

diff --git a/doc/lispref/tips.texi b/doc/lispref/tips.texi
index 9f6420949de..eb038164752 100644
--- a/doc/lispref/tips.texi
+++ b/doc/lispref/tips.texi
@@ -158,9 +158,10 @@ If the purpose of a function is to tell you whether a certain
 condition is true or false, give the function a name that ends in
 @samp{p} (which stands for ``predicate'').  If the name is one word,
 add just @samp{p}; if the name is multiple words, add @samp{-p}.
-Examples are @code{framep} and @code{frame-live-p}.  This predicate
-suffix should not be used in variable names (i.e., you should name a
-variable @code{foo-feature} instead of @code{foo-feature-p}).
+Examples are @code{framep} and @code{frame-live-p}.  We recommend to
+avoid using this @code{-p} suffix in boolean variable names, unless
+the variable is bound to a predicate function; instead, use a
+@code{-flag} suffix or names like @code{is-foo}.
 
 @item
 If the purpose of a variable is to store a single function, give it a