From: Richard Stallman <rms@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org
Subject: Re: library/package filename prefixes
Date: Sat, 02 May 2020 23:39:32 -0400 [thread overview]
Message-ID: <E1jV5TY-0000qc-4O@fencepost.gnu.org> (raw)
In-Reply-To: <bd915695-9b5d-4c8f-9732-8a73dda5ce78@default> (message from Drew Adams on Fri, 1 May 2020 14:07:14 -0700 (PDT))
[[[ 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. ]]]
> I think the "Emacs Lisp Coding Conventions" node
> of the Elisp manual should be amended to say that
> a library/package prefix should be at least 2
> chars followed by a hyphen (`-'). And even add
> that 3 or more is preferable.
I agree. Indeed, why not make 3 the minimum for users?
Are there any libraries in Emacs or GNU ELPA
which currently use a 2-letter prefix?
We could ask people to use at least 4 letters for prefixes invented
after today.
We could make special exceptions on rare occasions.
> "Too clever by half" is an expression that comes
> to mind. Cute, but not great for playing in the
> communal sandbox.
Well put!
--
Dr Richard Stallman
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2020-05-03 3:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 21:07 library/package filename prefixes Drew Adams
2020-05-02 18:35 ` Yuan Fu
2020-05-03 3:39 ` Richard Stallman [this message]
2020-05-03 4:17 ` Stefan Monnier
2020-05-04 3:08 ` Richard Stallman
2020-05-04 12:13 ` Eric Ludlam
2020-05-04 14:30 ` Eli Zaretskii
2020-05-04 15:49 ` Stefan Monnier
2020-05-04 16:19 ` Drew Adams
2020-05-05 2:51 ` Richard Stallman
2020-05-05 4:39 ` Drew Adams
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=E1jV5TY-0000qc-4O@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=drew.adams@oracle.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).