# HG changeset patch
# User Richard M. Stallman <rms@gnu.org>
# Date 783723869 0
# Node ID d5fa87d62d62b34b4117eccdb188ba6b2245e42d
# Parent  7542dbfaea1822df4731e07587c6e38e424af83e
Add function and variable name conventions.

diff -r 7542dbfaea18 -r d5fa87d62d62 lispref/tips.texi
--- a/lispref/tips.texi	Tue Nov 01 19:27:21 1994 +0000
+++ b/lispref/tips.texi	Tue Nov 01 21:04:29 1994 +0000
@@ -74,6 +74,16 @@
 @code{run-hooks}, just as the existing major modes do.  @xref{Hooks}.
 
 @item
+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}.  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}.
+
+@item
+If a user option variable records a true-or-false condition, give it a
+name that ends in @samp{-flag}.
+
+@item
 Please do not define @kbd{C-c @var{letter}} as a key in your major
 modes.  These sequences are reserved for users; they are the
 @strong{only} sequences reserved for users, so we cannot do without