From: Protesilaos Stavrou <info@protesilaos.com>
To: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: [GNU ELPA] Denote version 1.0.0
Date: Sun, 02 Oct 2022 10:23:50 +0300 [thread overview]
Message-ID: <87sfk66649.fsf@protesilaos.com> (raw)
In-Reply-To: <E1oenTc-00047F-O4@fencepost.gnu.org>
> From: Richard Stallman <rms@gnu.org>
> Date: Sat, 1 Oct 2022 21:09:04 -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. ]]]
>
> > >> Version 1.0.0 of package Denote has just been released in GNU ELPA.
> > >> You can now find it in M-x package-list RET.
> > >>
> > >> Denote describes itself as:
> > >> Simple notes with an efficient file-naming scheme
>
> The name "Denote" is an example of a class of clever names that we can
> call "half-helpful".
>
> Why half-helpful? Because once you know that "Denote" refers to
> "taking notes", you will probably remember that. When you see the name
> "Denote", you will recall what the package is good for.
>
> Why only half helpful? Because if you see only the name "Denote"
> without the clue, you won't have the faintest idea what the package is
> good for. This initial mystery is what makes the name amusingly
> clever.
>
> Can we come up with documentation conventions, for use when mentioning
> these half-helpful names, that will systematicall give the clue about
> each?
In principle, I am happy to conform with such conventions. Some notes:
* The 'M-x list-packages' includes a one-line description. Those
usually suffice to explain what the package tries to achieve.
* Any convention of this sort should not nudge us towards favouring
generic names like "emacs-notes", "notes-mode", "notes.el", etc.
There are lots of packages out there that have similar functionality.
If we all go for the generic name, we will keep clashing with each
other.
* Generic names can make it more difficult for core Emacs to introduce
new features. For example, we recently got 'emoji.el'. If some
package had already taken this name, it would complicate things for
the respective maintainers.
--
Protesilaos Stavrou
https://protesilaos.com
next prev parent reply other threads:[~2022-10-02 7:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <85czbd44kc.fsf@elpa.gnu.org>
[not found] ` <87mtah447f.fsf@protesilaos.com>
[not found] ` <jwvh70o7txf.fsf-monnier+emacs@gnu.org>
2022-10-02 1:09 ` [GNU ELPA] Denote version 1.0.0 Richard Stallman
2022-10-02 7:23 ` Protesilaos Stavrou [this message]
2022-10-09 23:02 ` 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=87sfk66649.fsf@protesilaos.com \
--to=info@protesilaos.com \
--cc=emacs-devel@gnu.org \
--cc=rms@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).