From: Drew Adams <drew.adams@oracle.com>
To: Chad Brown <yandros@gmail.com>, emacs-devel <emacs-devel@gnu.org>
Cc: Teemu Likonen <tlikonen@iki.fi>
Subject: RE: Document that symbol prefix "my-" (or other) should be left for users
Date: Tue, 15 Dec 2015 17:52:36 -0800 (PST) [thread overview]
Message-ID: <91db4ff0-18af-48c3-801d-7e1f7611d31e@default> (raw)
In-Reply-To: <CCD94F9B-D83D-422F-B077-F5E1CBD3E3E1@gmail.com>
> > So can you give a reason why Emacs-Lisp coding conventions
> > should reserve such a prefix (or any other) for users?
> > Haven't heard any reason, so far.
>
> I have seen people run into conflicts several times (over a
> long time frame)... So: if you want to know if it has ever
> happened: absolutely.
The question I raised is not whether users have run into name
conflicts but why Emacs coding conventions should reserve any
given name prefix (or prefixes?) for users.
Users can run into name conflicts also if they use the same
"reserved" prefix `my-' (or `my/' or `my31459265358979535/'
or whatever).
next prev parent reply other threads:[~2015-12-16 1:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-13 18:16 Document that symbol prefix "my-" (or other) should be left for users Teemu Likonen
2015-12-13 18:32 ` Drew Adams
2015-12-13 18:56 ` Teemu Likonen
2015-12-14 20:31 ` John Wiegley
2015-12-15 18:22 ` Tassilo Horn
2015-12-15 18:29 ` John Yates
2015-12-15 19:01 ` Drew Adams
2015-12-15 20:32 ` John Wiegley
2015-12-16 3:12 ` Evans Winner
2015-12-16 6:41 ` John Wiegley
2015-12-16 0:16 ` David Reitter
2015-12-16 1:26 ` Drew Adams
2015-12-16 1:39 ` Chad Brown
2015-12-16 1:52 ` Drew Adams [this message]
2015-12-16 4:41 ` Chad Brown
-- strict thread matches above, loose matches on Subject: below --
2022-07-10 3:39 Special Event: Davin reveals his own personal additions to Emacs Davin Pearson
2022-07-10 12:57 ` Stefan Monnier
2022-07-10 16:03 ` Document that symbol prefix "my-" (or other) should be left for users Teemu Likonen
2022-07-10 16:59 ` Stefan Kangas
2022-07-10 18:11 ` Bozhidar Batsov
2022-07-10 19:20 ` Tim Cross
2022-07-11 3:17 ` Richard Stallman
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=91db4ff0-18af-48c3-801d-7e1f7611d31e@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=tlikonen@iki.fi \
--cc=yandros@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 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.