unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jim Porter <jporterbugs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, Payas Relekar <relekarpayas@gmail.com>
Cc: rms@gnu.org, philipk@posteo.net, susam.pal@gmail.com,
	emacs-devel@gnu.org
Subject: Re: [NonGNU ELPA] New package: devil
Date: Fri, 12 May 2023 09:19:55 -0700	[thread overview]
Message-ID: <e6c7d9b9-f319-093b-ddfa-053e21c6b4f1@gmail.com> (raw)
In-Reply-To: <83y1lv5qe9.fsf@gnu.org>

On 5/10/2023 11:33 PM, Eli Zaretskii wrote:
> Please reconsider, I think this name is very unfortunate, because it
> gives users no clue whatsoever about the package's purpose.

How about something like "devil-keys"? That should make it clear that 
the package has something to do with keys. It doesn't tell exactly what 
it *does* with those keys, but I think a more-detailed description 
belongs in the package description or the manual.

Within the package itself, I think it would be fine to refer to it as 
"Devil" (without the "-keys"), since once you're looking at the package 
in detail, the "keys" hint isn't needed anymore.



  parent reply	other threads:[~2023-05-12 16:19 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-11  5:23 [NonGNU ELPA] New package: devil Payas Relekar
2023-05-11  6:26 ` Po Lu
2023-05-11  6:33 ` Eli Zaretskii
2023-05-11  6:52   ` Philip Kaludercic
2023-05-11  7:07     ` Eli Zaretskii
2023-05-12 15:02       ` Brian Cully via Emacs development discussions.
2023-05-11  8:09     ` Susam Pal
2023-05-11  8:45       ` Philip Kaludercic
2023-05-11  8:58         ` Eli Zaretskii
2023-05-11  9:08           ` Susam Pal
2023-05-11  9:12             ` Philip Kaludercic
2023-05-11  9:19               ` Susam Pal
2023-05-11  9:34                 ` Ruijie Yu via Emacs development discussions.
2023-05-11 10:09                   ` Susam Pal
2023-05-11 10:31                     ` Susam Pal
2023-05-11 10:36             ` Eli Zaretskii
2023-05-11  8:56       ` Eli Zaretskii
2023-05-12 16:19   ` Jim Porter [this message]
2023-05-13  7:10     ` Philip Kaludercic
2023-05-13  9:05       ` Susam Pal
2023-05-15 22:12         ` Richard Stallman
2023-05-17 13:30         ` João Távora
2023-05-17 14:06           ` Philip Kaludercic
2023-05-17 15:41             ` João Távora
2023-05-17 15:46               ` Eli Zaretskii
2023-05-13 22:30     ` Richard Stallman
2023-05-14  4:29       ` Naming guidelines for ELPA packages (was: Re: [NonGNU ELPA] New package: devil) Jim Porter
2023-05-14  7:47         ` Naming guidelines for ELPA packages Philip Kaludercic
2023-05-14 19:23           ` Jim Porter
2023-05-14 19:33             ` Philip Kaludercic
2023-05-19  3:49               ` Jim Porter
2023-05-19  4:33                 ` Akib Azmain Turja
2023-05-20 16:51                   ` Philip Kaludercic
2023-05-21 21:03                   ` Richard Stallman
2023-05-14 21:36         ` Stefan Monnier via Emacs development discussions.
2023-05-14 22:17           ` Jim Porter
2023-05-14 23:00             ` Stefan Monnier
2023-05-15  1:36               ` Jim Porter
2023-05-15 22:15         ` Naming guidelines for ELPA packages (was: Re: [NonGNU ELPA] New package: devil) Richard Stallman
2023-05-15 22:15         ` Richard Stallman
2023-05-16  4:51           ` Jim Porter
2023-05-16  8:42           ` Naming guidelines for ELPA packages Madhu
  -- strict thread matches above, loose matches on Subject: below --
2023-05-09  1:57 [NonGNU ELPA] New package: devil Susam Pal
2023-05-09  8:42 ` Philip Kaludercic
2023-05-09  8:52   ` Eli Zaretskii
2023-05-09  8:58     ` Philip Kaludercic
2023-05-09 18:19       ` chad
2023-05-09 22:07         ` Susam Pal
2023-05-09 20:56   ` Susam Pal
2023-05-10  6:09     ` Philip Kaludercic
2023-05-10 21:00       ` Susam Pal
2023-05-10 21:56       ` 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=e6c7d9b9-f319-093b-ddfa-053e21c6b4f1@gmail.com \
    --to=jporterbugs@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=philipk@posteo.net \
    --cc=relekarpayas@gmail.com \
    --cc=rms@gnu.org \
    --cc=susam.pal@gmail.com \
    /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).