From: Adam Porter <adam@alphapapa.net>
To: emacs-devel@gnu.org
Subject: Re: library prefixes (versus other name prefixes)
Date: Sun, 03 May 2020 10:07:39 -0500 [thread overview]
Message-ID: <87r1w16oqs.fsf@alphapapa.net> (raw)
In-Reply-To: 73dcba36-03d1-408e-84ac-b07edde8ef77@default
If I may offer a perspective from "MELPA land" (though I am not MELPA,
just a contributor):
MELPA has not always required that submitted packages strictly adhere to
the Elisp manual's conventions, so some older packages do use a slash as
a prefix separator.
New packages are frequently submitted which use a slash separator. Now,
MELPA requires them to replace the slash with a hyphen, as the Elisp
manual recommends. Sometimes the package authors are very reluctant to
do so.
Some built-in Emacs packages also use a slash separator, like pcomplete
(although it seems to use it only for generated completion functions,
not library functions).
Some MELPA packages also use a colon as a separator, like Hydra
(although, like pcomplete, it seems to use it only for generated Hydra
functions).
In my own non-MELPA code, I use a slash separator. For me, it's more
visually distinctive than a hyphen and makes it easier to discern the
prefix part of the symbol.
So, I would be glad if the official Elisp conventions allowed a slash
separator, and I think many other Elisp package authors would as well.
This topic frequently comes up in discussion on reddit.com/r/emacs,
which is read by many users and package authors, so I've linked this
thread there:
https://old.reddit.com/r/emacs/comments/gcrwic/the_symbolprefixseparatormustbeahyphen_topic/
prev parent reply other threads:[~2020-05-03 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 19:35 library prefixes (versus other name prefixes) Drew Adams
2020-05-03 15:07 ` Adam Porter [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r1w16oqs.fsf@alphapapa.net \
--to=adam@alphapapa.net \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.