From: Drew Adams <drew.adams@oracle.com>
To: Artur Malabarba <arturmalabarba@gmail.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>,
Marcin Borkowski <mbork@wmi.amu.edu.pl>
Subject: RE: A question about cycle-spacing--context
Date: Sun, 25 Jan 2015 19:10:52 -0800 (PST) [thread overview]
Message-ID: <21ab2475-2b68-43c3-8e3a-2ee4c19356a7@default> (raw)
In-Reply-To: <CAAdUY-LOKZTJa30bFNf-WfsudYi4vep7mT=a-On-yseNMWm5JQ@mail.gmail.com>
> > Some of the Emacs developers like to use `--' to indicate an
>
> As of 24.4, this is also the official recommended style.
> At least, (I think) that's what it said in the news file.
Same difference. ;-) See what I wrote about what "internal" means
for something like Emacs:
its implementation is not guaranteed not to change
(which is anyway true of any function, var or whatever!).
IOW, much ado about little or nothing. Just one opinion, of course.
(BTW, I see nothing in NEWS about this, by searching for "--"
or "[Ii]nternal". The only thing mentioned is that for `cl-lib'
the "internal definitions use the 'cl--' prefix" - and that is
mentioned for Emacs 24.3, not 24.4.)
Personally, I do use the same convention occasionally, but
usually to remind *myself* that the thing in question is
something whose implementation I probably do *not* want to
change lightly. IOW, in my case it is for the code developer,
not for someone using the code, and it just reminds me that
this stuff is essentially "plumbing".
(BTW2: In a `simple.el' name such as
`repeat-complex-command--called-interactively-skip' (gotta
love that one), added for Emacs 24.4 and removed since, one
wonders whether the `--' might have been introduced less
because the thing was considered internal and more just to
visually separate the `repeat-complex-command' prefix from
the rest of the name, IOW, as a kind of compensation.)
prev parent reply other threads:[~2015-01-26 3:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-25 23:28 A question about cycle-spacing--context Marcin Borkowski
2015-01-26 0:38 ` Drew Adams
2015-01-26 1:48 ` Artur Malabarba
2015-01-26 3:10 ` Drew Adams [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
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=21ab2475-2b68-43c3-8e3a-2ee4c19356a7@default \
--to=drew.adams@oracle.com \
--cc=arturmalabarba@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=mbork@wmi.amu.edu.pl \
/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.
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).