unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: jorge.alfaro-murillo@yale.edu (Jorge A. Alfaro-Murillo)
To: emacs-devel@gnu.org
Subject: Re: [PATCH] timer-list -> list-timers?
Date: Wed, 20 Sep 2017 12:17:31 -0400	[thread overview]
Message-ID: <87d16ljqec.fsf@yale.edu> (raw)
In-Reply-To: 87poale8vj.fsf@lifelogs.com

Ted Zlatanov writes:

> On Sat, 16 Sep 2017 20:56:53 +0200 Lars Ingebrigtsen 
> <larsi@gnus.org> wrote:  
> 
> LI> I guess I was just adhering to the `<package>-function' 
> naming LI> convention.  I'm all for renaming it to 
> `list-timers'. 
> 
> 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? 

I agree. These functions that don't follow the package naming 
convention are always hard to find. Wouldn't `timer-list-timers', 
`package-list-packages', `holidays-list-holidays', etc be better?
-- 
Jorge.




  reply	other threads:[~2017-09-20 16:17 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 [this message]
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
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=87d16ljqec.fsf@yale.edu \
    --to=jorge.alfaro-murillo@yale.edu \
    --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).