From: Drew Adams <drew.adams@oracle.com>
To: rms@gnu.org
Cc: eliz@gnu.org, boruch_baum@gmx.com, emacs-devel@gnu.org
Subject: RE: adding to emacs coding standard / formatting
Date: Wed, 21 Oct 2020 07:46:11 -0700 (PDT) [thread overview]
Message-ID: <4f0970a9-a27f-44f7-b8af-a1a5762e1c34@default> (raw)
In-Reply-To: <E1kV5ry-000192-6W@fencepost.gnu.org>
> > But what does this have to do with coding
> > conventions? (Let alone why would such usage be
> > "banned".)
>
> > This is on the order of helpful tips, not coding
> > conventions, IMO.
>
> For users, it should be a tip.
> However, we might want to insist on this for code in Emacs, GNU ELPA
> or NonGNU ELPA when we have that.
Yes, that was my thought exactly. Thanks for stating
it plainly.
The coding conventions in the manual serve a double
purpose. Things mentioned there are (1) pretty much
mandatory for inclusion in Emacs and (2) recommendations
for other Elisp code (e.g. user/3rd-party).
next prev parent reply other threads:[~2020-10-21 14:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 3:10 adding to emacs coding standard / formatting Boruch Baum
2020-10-19 9:28 ` Stefan Kangas
2020-10-19 15:37 ` Drew Adams
2020-10-19 14:24 ` Stefan Monnier
2020-10-19 14:32 ` Eli Zaretskii
2020-10-19 19:59 ` Boruch Baum
2020-10-19 20:07 ` Drew Adams
2020-10-21 4:37 ` Richard Stallman
2020-10-21 14:46 ` Drew Adams [this message]
2020-10-20 5:11 ` Richard Stallman
2020-10-20 5:11 ` Richard Stallman
2020-10-20 5:55 ` Boruch Baum
2020-10-20 8:32 ` Eli Zaretskii
2020-10-20 9:30 ` Jean Louis
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=4f0970a9-a27f-44f7-b8af-a1a5762e1c34@default \
--to=drew.adams@oracle.com \
--cc=boruch_baum@gmx.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@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.
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).