unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: RE: Naming predicates (was: master d0c77a1: Remove some assumptions about timestamp format)
Date: Fri, 28 Sep 2018 11:28:32 -0700 (PDT)	[thread overview]
Message-ID: <2a1f7389-0248-4920-ba11-ecc0b6aaee22@default> (raw)
In-Reply-To: <jwvsh1twldg.fsf-monnier+gmane.emacs.devel@gnu.org>

> >> Shouldn't this be `time-equal-p', as we have already `time-less-p'?
> > Thanks, as a Scheme refugee I never can remember which predicates should end
> > in "-p" vs "p" vs nothing. I installed the attached.
> 
> The rule is not that bad: use a "-p or p" suffix whenever a Schemer
> would use a "?" suffix.  As for when to use "-p" vs just "p" I'd say you
> can simply always use "-p" when it's something you define.

I'd say that as a user you can use whatever you want - i.e., "when it's something you define".

But there is an Emacs convention, and it's not difficult to find or to follow, for those so inclined:

In the Elisp manual, `i convention' shows you this index-entry candidate (*), among others: 

  `coding conventions in Emacs Lisp'

And choosing that takes you directly to, well, the coding conventions for Emacs Lisp (!), where you find this:

  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
  'p' (which stands for "predicate").  If the name is one word, add
  just 'p'; if the name is multiple words, add '-p'.  Examples are
  'framep' and 'frame-live-p'.

_______
* Well, it shows you that candidate if you've configured Emacs option `completion-styles' to include substring matching. Or if you use something like Icicles. If not then, because that index entry doesn't start with "convention", it won't show up. In that case, you need to know to try `coding TAB' instead of `convention TAB'.



  reply	other threads:[~2018-09-28 18:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180925021527.10418.61555@vcs0.savannah.gnu.org>
     [not found] ` <20180925021528.9A119204E8@vcs0.savannah.gnu.org>
2018-09-25 10:09   ` master d0c77a1: Remove some assumptions about timestamp format Michael Albinus
2018-09-26  1:09     ` Paul Eggert
2018-09-26  9:24       ` Michael Albinus
2018-09-26  9:39         ` Eli Zaretskii
2018-09-26  9:43           ` Michael Albinus
2018-09-27 20:46         ` Paul Eggert
2018-09-28  6:32           ` Eli Zaretskii
2018-09-28 10:26             ` Michael Albinus
2018-09-28 17:27               ` Paul Eggert
2018-09-29 13:35                 ` Michael Albinus
2018-09-28 14:45             ` Paul Eggert
2018-09-28 14:54               ` Michael Albinus
2018-09-28  1:50         ` Paul Eggert
2018-09-28 10:35           ` Michael Albinus
2018-09-28 17:39             ` Paul Eggert
2018-09-28 18:06               ` Naming predicates (was: master d0c77a1: Remove some assumptions about timestamp format) Stefan Monnier
2018-09-28 18:28                 ` Drew Adams [this message]
2018-09-28 19:12                   ` Paul Eggert
2018-09-28 19:26                     ` Naming predicates Stefan Monnier
2018-09-28 19:40                       ` Drew Adams
2018-09-28 19:41                     ` Naming predicates (was: master d0c77a1: Remove some assumptions about timestamp format) 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=2a1f7389-0248-4920-ba11-ecc0b6aaee22@default \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).