From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: [PATCH] timer-list -> list-timers?
Date: Thu, 21 Sep 2017 10:24:42 -0400 [thread overview]
Message-ID: <87a81odt91.fsf@lifelogs.com> (raw)
In-Reply-To: 87o9q4yjpu.fsf@udel.edu
On Sat, 16 Sep 2017 11:11:00 -0400 Mark Oteiza <mvoteiza@udel.edu> wrote:
MO> While I understand there is a push to keep everything always in its
MO> own "namespace", list-foo is its own namespace, and is a useful one
MO> that collects special listings of different things around emacs.
On Wed, 20 Sep 2017 20:32:45 -0400 Mark Oteiza <mvoteiza@udel.edu> wrote:
MO> jorge.alfaro-murillo@yale.edu (Jorge A. Alfaro-Murillo) writes:
>> So, I also have the same question as Ted: when is there a good reason
>> to not follow the `<package>-' naming convention?
MO> One was stated in the OP.
I saw it, but it was a bit ambiguous.
A better guideline *might* be "if the *command* PACKAGE-list or
PACKAGE-list-foo is in the core, loaded by default, and accessible
through the menubar; and it brings up a standalone buffer listing
objects with which the user can interact; it should have a
`list-PACKAGE` or `list-foo' alias also loaded by default." This is
less ambiguous. It could even be checked by a style checker. We can
discuss the exact wording but I hope you see what I mean.
Ted
next prev parent reply other threads:[~2017-09-21 14:24 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 [this message]
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
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=87a81odt91.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@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).