unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Mark Oteiza <mvoteiza@udel.edu>
Cc: jorge.alfaro-murillo@yale.edu, emacs-devel@gnu.org
Subject: Re: [PATCH] timer-list -> list-timers?
Date: Thu, 21 Sep 2017 14:28:54 -0400	[thread overview]
Message-ID: <E1dv6DW-0007f5-Vf@fencepost.gnu.org> (raw)
In-Reply-To: <87vakcyjt2.fsf@udel.edu> (message from Mark Oteiza on Wed, 20 Sep 2017 20:30:49 -0400)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > >> That kind of bugs me about `M-x list-packages' etc. (there's a whole
  > >> bunch of them, like `list-holidays' and so on). Is there any rule
  > >> about when to make an exception to the `<package>-function' naming
  > >> convention?  If not, should there be one? 

The convention is that functions in a package (and variables) should
have names which show their relationship to that package.  Usually we
do that by using the package name as a prefix, but that is not the
only way to do it.  It is ok to use the package name (or some form of
it) later on in the name.

So if there is a package called frob that works with things called frobs,
it is natural and ok for it to contain a command 'list-frobs'.

-- 
Dr Richard Stallman
President, Free Software Foundation (gnu.org, fsf.org)
Internet Hall-of-Famer (internethalloffame.org)
Skype: No way! See stallman.org/skype.html.




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

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-16 15:11 [PATCH] timer-list -> list-timers? Mark Oteiza
2017-09-16 15:31 ` raman
2017-09-16 16:59 ` Eli Zaretskii
2017-09-16 17:02   ` Eli Zaretskii
2017-09-16 18:56   ` Lars Ingebrigtsen
2017-09-17  3:13     ` Mark Oteiza
2017-09-19 23:39     ` John Wiegley
2017-09-20 11:41       ` Mark Oteiza
2017-09-20 14:34     ` Ted Zlatanov
2017-09-20 16:17       ` Jorge A. Alfaro-Murillo
2017-09-20 18:52         ` Tom Tromey
2017-09-20 19:37         ` Eli Zaretskii
2017-09-20 22:29           ` Jorge A. Alfaro-Murillo
2017-09-21  0:32             ` Mark Oteiza
2017-09-21 14:24               ` Ted Zlatanov
2017-09-21 14:35               ` Jorge A. Alfaro-Murillo
2017-09-21  7:43             ` Eli Zaretskii
2017-09-21  0:30         ` Mark Oteiza
2017-09-21 18:28           ` Richard Stallman [this message]
2017-09-20 17:49       ` Drew Adams
2017-09-21 18:26         ` Richard Stallman

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=E1dv6DW-0007f5-Vf@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jorge.alfaro-murillo@yale.edu \
    --cc=mvoteiza@udel.edu \
    /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).