From: Juanma Barranquero <lekktu@gmail.com>
To: Zachary Kanfer <zkanfer@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Proposal to change naming format to allow package-prefix/function-name
Date: Mon, 30 Dec 2019 13:03:45 +0100 [thread overview]
Message-ID: <CAAeL0SR2d-BVzSr-mt-AuSqCR-tzHgPucyD2+uvdfiN=-Ty6hQ@mail.gmail.com> (raw)
In-Reply-To: <CAFXT+RO8NW55oqLGJUJoVbdC9Xu=oFSPsX3Mgu6Em0Rg1mzVNQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 940 bytes --]
On Mon, Dec 30, 2019 at 8:03 AM Zachary Kanfer <zkanfer@gmail.com> wrote:
> Some Elisp functions that are part of Emacs already follow this format.
> 1. Many eshell functions already follow this format, for example
eshell/ls, eshell/exit, and eshell/define.
> 2. Pcomplete functions use this format, even some for more than one
hierarchical level, e.g. pcomplete/gzip,
pcomplete/erc-mode/complete-command, pcomplete/org-mode/block-option/src.
> 3. Org-plot has half a dozen functions, like org-plot/goto-nearest-table.
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).
[-- Attachment #2: Type: text/html, Size: 1070 bytes --]
next prev parent reply other threads:[~2019-12-30 12:03 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 [this message]
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
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='CAAeL0SR2d-BVzSr-mt-AuSqCR-tzHgPucyD2+uvdfiN=-Ty6hQ@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=emacs-devel@gnu.org \
--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).