From: Lars Ingebrigtsen <larsi@gnus.org>
To: Adam Porter <adam@alphapapa.net>
Cc: emacs-devel@gnu.org
Subject: Re: Proposal to change naming format to allow package-prefix/function-name
Date: Tue, 31 Dec 2019 11:14:47 +0100 [thread overview]
Message-ID: <87h81gdco8.fsf@gnus.org> (raw)
In-Reply-To: <87imlxjr46.fsf@alphapapa.net> (Adam Porter's message of "Mon, 30 Dec 2019 18:06:17 -0600")
Adam Porter <adam@alphapapa.net> writes:
> Whatever the character used, as long as it's visually distinctive and
> easy to type, I think it would be helpful to both users and developers
> to allow it to be used to separate the package/feature name from the
> rest of the symbol name.
I don't. In Common Lisp, it's a functional thing, and it's easy to
remember that foo:bar-zot is a thing, but in Emacs Lisp, where it would
just be a character that's not sounded when you read the symbol, it's
just confounding. In the past, when working on Emacs Lisp code bases
where somebody has been creative with non-letter characters, I always
find myself having to try all the variations to find the correct symbol,
because what my brain remembers is "foo bar zot", and not whatever is in
between those letters.
foo:bar-zot? foo-bar:zot? foo:bar/zot?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-12-31 10:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 7:02 Proposal to change naming format to allow package-prefix/function-name Zachary Kanfer
2019-12-30 12:03 ` Juanma Barranquero
2019-12-30 13:12 ` Elias Mårtenson
2019-12-30 21:50 ` Zachary Kanfer
2019-12-31 0:45 ` Richard Stallman
2020-01-02 18:32 ` Sam Steingold
2019-12-31 0:06 ` Adam Porter
2019-12-31 10:14 ` Lars Ingebrigtsen [this message]
2019-12-31 10:54 ` Ihor Radchenko
2019-12-31 12:06 ` Clemens Radermacher
2019-12-31 14:48 ` Teemu Likonen
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=87h81gdco8.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=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 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).