From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: [External] : A peek to the other side
Date: Tue, 22 Feb 2022 20:43:02 +0200 [thread overview]
Message-ID: <83czjeu4i1.fsf@gnu.org> (raw)
In-Reply-To: <SJ0PR10MB5488DC9B38CF5196D233C25CF33B9@SJ0PR10MB5488.namprd10.prod.outlook.com> (message from Drew Adams on Tue, 22 Feb 2022 18:25:44 +0000)
> From: Drew Adams <drew.adams@oracle.com>
> Date: Tue, 22 Feb 2022 18:25:44 +0000
> Cc: "'Help-Gnu-Emacs \(help-gnu-emacs@gnu.org\)'" <help-gnu-emacs@gnu.org>
>
> At the very least, every use of `--' should have an
> easily findable comment or doc, explaining what it's
> about - why the labeler labeled it so. A guess is
> that if that guideline were adopted there'd be a lot
> less gratuitous use (misuse) of `--'. And updating
> out-of-date `--' would be less problematic. Today,
> it's an irresponsible, easy "label `--' willy nilly,
> and forget about it."
You make it sound like we are too lazy to do this stuff, so we use a
cop-out.
Nothing is farther from the truth. The free time we have to work on
Emacs is used to its last second. There's only so much one can do in
a given time, and it is therefore wise to prioritize the jobs and do
the more important ones first. Abundantly documenting APIs we
consider to be internal, not-for-use, subject-to-change-without-notice
is way down the priority list, that's all. So we keep the
documentation of those to the absolute minimum: by using the "--"
indication, and we expect Emacs programmers to trust us on that.
Anything else would simply be a case of bad judgment and misuse of the
time we have to contribute.
next prev parent reply other threads:[~2022-02-22 18:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 7:11 A peek to the other side emacsq via Users list for the GNU Emacs text editor
2022-02-22 16:11 ` [External] : " Drew Adams
2022-02-22 16:46 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-02-22 18:25 ` Drew Adams
2022-02-22 18:43 ` Eli Zaretskii [this message]
2022-02-22 19:38 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-02-26 3:45 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-23 12:24 ` Arthur Miller
2022-02-23 13:50 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-02-26 3:36 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-22 18:21 ` Samuel Banya
2022-02-22 19:17 ` Philip Kaludercic
2022-02-22 21:31 ` Samuel Banya
2022-02-23 12:05 ` Arthur Miller
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=83czjeu4i1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).