From: Kaushal Modi <kaushal.modi@gmail.com>
To: 26564@debbugs.gnu.org
Subject: bug#26564: Document that only functions and not variables can end with "-p"
Date: Wed, 19 Apr 2017 15:47:06 +0000 [thread overview]
Message-ID: <CAFyQvY2Jhe7d7tFMgqQH+oHOHhx2_OXT3UBDYqjbUaXLw-KrNg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1195 bytes --]
The discussion on whether variables should end in "-p" came up few time on
emacs-devel, at least the ones I was part of:
1. https://lists.gnu.org/archive/html/emacs-devel/2016-07/msg00734.html
2. http://lists.gnu.org/archive/html/emacs-devel/2017-04/msg00540.html
Doing a rudimentary search in emacs/lisp/ code-base shows a sign of an
undocumented convention that predicate functions, functions that return
either nil or non-nil can end in "-p" (if the function name is multi-word,
like nested-alist-p), or just "p" (if the function name is a single word,
like stringp).
I ran ag[1] in emacs/lisp:
1. 1511 matches -- defuns and defsubsts ending in -p -- ag
'def(un|subst)\s+[^ ]+-p\s+' --stats
2. 149 matches -- defvars, defconsts and defcustoms ending in -p -- ag
'def(var|const|custom)\s+[^ ]+-p\s+' --stats
3. 65 matches -- Just the user-facing defcustoms -- ag 'defcustom\s+[^
]+-p\s+' --stats
That corroborates that more functions tend to end in "-p" than variables.
This bug report is to make a request to incorporate this unspoken rule as a
rule in the Elisp manual.
What would be the correct section to do so?
[1]: https://github.com/ggreer/the_silver_searcher
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 2080 bytes --]
next reply other threads:[~2017-04-19 15:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 15:47 Kaushal Modi [this message]
2017-04-19 16:08 ` bug#26564: Document that only functions and not variables can end with "-p" Eli Zaretskii
2017-04-19 16:22 ` Kaushal Modi
2017-04-19 21:49 ` Michael Heerdegen
2017-04-19 22:04 ` Drew Adams
2017-04-19 22:18 ` Michael Heerdegen
2019-10-12 20:27 ` Lars Ingebrigtsen
2019-10-12 20:47 ` Kaushal Modi
2019-10-12 23:18 ` Drew Adams
2019-10-14 1:50 ` Richard Stallman
2019-10-14 2:22 ` Drew Adams
2019-10-14 7:24 ` Eli Zaretskii
2019-10-14 7:21 ` Eli Zaretskii
2017-04-19 17:26 ` Drew Adams
2017-04-19 21:44 ` Michael Heerdegen
2017-04-19 22:01 ` Drew Adams
2017-04-19 22:23 ` Michael Heerdegen
2017-04-19 22:28 ` Drew Adams
2017-04-20 1:42 ` Drew Adams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFyQvY2Jhe7d7tFMgqQH+oHOHhx2_OXT3UBDYqjbUaXLw-KrNg@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--cc=26564@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).