From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Bozhidar Batsov <bozhidar@batsov.dev>,
akater <nuclearspace@gmail.com>,
Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Codifying some aspects of Elisp code style and improving pretty printer
Date: Fri, 01 Oct 2021 16:43:29 +0200 [thread overview]
Message-ID: <874ka0x0tq.fsf@gnus.org> (raw)
In-Reply-To: <jwvy27crfuy.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 01 Oct 2021 10:20:46 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> I guess there is room for a *description* of the coding style that
> happens to be currently in use. Especially if it comes with sufficient
> caveats to clarify that it's not a rule book.
Yeah, sure -- a section of "things we think are rather spiffy when
formatting Emacs Lisp" would be nice. With lots of examples.
> E.g. it could have a few rules, together with a percentage of how often
> it is followed. Could be quite useful for ethnography and maybe also
> comparative "literature", or to classify Free Software projects based on
> their preferred coding styles.
Heh heh heh.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-10-01 14:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 18:01 Codifying some aspects of Elisp code style and improving pretty printer akater
2021-09-30 7:02 ` André A. Gomes
2021-09-30 11:26 ` Bozhidar Batsov
2021-09-30 15:15 ` akater
2021-10-01 7:05 ` Lars Ingebrigtsen
2021-10-01 14:20 ` Stefan Monnier
2021-10-01 14:43 ` Lars Ingebrigtsen [this message]
2021-10-01 14:26 ` Robert Pluim
2021-10-01 15:26 ` Stefan Monnier
2021-10-01 16:15 ` Robert Pluim
2021-10-01 17:08 ` Stefan Monnier
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=874ka0x0tq.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=bozhidar@batsov.dev \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=nuclearspace@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).