From: "Elias Mårtenson" <lokedhs@gmail.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Zachary Kanfer <zkanfer@gmail.com>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: Proposal to change naming format to allow package-prefix/function-name
Date: Mon, 30 Dec 2019 16:12:23 +0300 [thread overview]
Message-ID: <CADtN0WJaU0dTKWGkXJ5Sb93PU3g_n5WmvNAVuTMwTBu55fBpzA@mail.gmail.com> (raw)
In-Reply-To: <CAAeL0SR2d-BVzSr-mt-AuSqCR-tzHgPucyD2+uvdfiN=-Ty6hQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 987 bytes --]
On Mon, 30 Dec 2019, 20:05 Juanma Barranquero, <lekktu@gmail.com> wrote:
>
> I think this proposal is unlikely to gain traction. But if it were, in a
> Lisp context colon (:) would make more sense IMHO, as it is used in Common
> Lisp to separate the namespace ("package", in CL-speak) from the symbol
> name. That would make easier to adapt to CL-style namespaces, if they were
> implemented in Emacs some day (which I think won't ever happen, if previous
> discussions on the subject are to be believed).
>
I just want to voice my 100% agreement that the minus character should be
changed. Its double use is, as mentioned in the original post, incredibly
annoying to read. In my package, gnu-apl-mode, all symbols are prefixed
with gbu-apl- and it's full of these issues.
Whether the character is / or : or anything else, I could not care less.
All I want is a symbol that isn't much used for anything else.
The benefit of / is that a lot of third party packages already use it.
>
[-- Attachment #2: Type: text/html, Size: 1618 bytes --]
next prev parent reply other threads:[~2019-12-30 13:12 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 [this message]
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
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=CADtN0WJaU0dTKWGkXJ5Sb93PU3g_n5WmvNAVuTMwTBu55fBpzA@mail.gmail.com \
--to=lokedhs@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=zkanfer@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).