From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Jonas Bernoulli <jonas@bernoul.li>
Cc: emacs-devel@gnu.org
Subject: Re: Regarding outline headings in emacs-lisp libraries
Date: Sun, 26 Jul 2020 14:23:40 -0400 [thread overview]
Message-ID: <jwvh7tujg4b.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87ft9el2bl.fsf@bernoul.li> (Jonas Bernoulli's message of "Sun, 26 Jul 2020 17:32:14 +0200")
> The best I can come up right now is "Front matter" and "Back matter".
> Or else "Code:" and "_" as suggested before. But hopefully someone else
> can think of something better.
I definitely don't want to rename "Code:" to something else.
It would be a rather gratuitous change, since "Code:" is basically the
only section that appears in virtually all Elisp files and renaming it
would provide very little concrete benefits.
As for the end: I'd rather simply not define a convention for it.
I'm not even sure what would be the benefit of such a convention
(unless there's really something substantial that will often end up
there, compared to the current situation where for most files it would
only contain the `provide` statement).
Stefan
next prev parent reply other threads:[~2020-07-26 18:23 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 21:48 Regarding outline headings in emacs-lisp libraries Jonas Bernoulli
2020-07-17 22:27 ` Stefan Monnier
2020-07-18 1:41 ` T.V Raman
2020-07-18 3:22 ` Stefan Monnier
2020-07-18 14:16 ` T.V Raman
2020-07-18 16:12 ` Stefan Monnier
2020-07-18 16:49 ` T.V Raman
2020-07-18 22:54 ` Jonas Bernoulli
2020-07-18 3:29 ` Stefan Monnier
2020-07-18 16:15 ` Drew Adams
2020-07-18 22:46 ` Jonas Bernoulli
2020-07-18 23:56 ` Drew Adams
2020-07-19 9:03 ` Jonas Bernoulli
2020-07-19 15:36 ` Drew Adams
2020-07-18 23:26 ` Jonas Bernoulli
2020-07-19 3:36 ` Stefan Monnier
2020-07-19 14:54 ` Eli Zaretskii
2020-07-26 13:49 ` Jonas Bernoulli
2020-07-26 14:11 ` Eli Zaretskii
2020-07-26 15:43 ` Jonas Bernoulli
2020-07-26 16:23 ` Eli Zaretskii
2020-07-26 18:25 ` Jonas Bernoulli
2020-07-26 14:40 ` Stefan Monnier
2020-07-26 15:32 ` Jonas Bernoulli
2020-07-26 17:00 ` Yuan Fu
2020-07-26 18:23 ` Stefan Monnier [this message]
2020-07-26 18:59 ` Eli Zaretskii
2020-07-26 19:45 ` Stefan Monnier
2020-07-28 13:41 ` Jonas Bernoulli
2020-07-28 14:30 ` Eli Zaretskii
2020-07-28 14:42 ` Jonas Bernoulli
2020-07-28 15:52 ` Eli Zaretskii
2020-07-28 14:48 ` Stefan Monnier
2020-07-26 21:11 ` Jonas Bernoulli
2020-07-26 18:34 ` Jonas Bernoulli
2020-07-26 18:55 ` [SPAM UNSURE] " Stephen Leake
2020-07-18 6:40 ` Eli Zaretskii
2020-07-28 19:18 ` Jonas Bernoulli
2020-07-29 14:34 ` Eli Zaretskii
2020-07-29 18:34 ` Jonas Bernoulli
2020-07-29 18:56 ` Eli Zaretskii
2020-08-01 2:53 ` Richard Stallman
2020-08-01 5:48 ` Eli Zaretskii
2020-08-01 21:13 ` Jonas Bernoulli
2020-08-01 23:10 ` T.V Raman
2020-08-02 1:01 ` Drew Adams
2020-08-02 16:15 ` Eli Zaretskii
2020-08-03 3:22 ` Stefan Monnier
2020-08-03 14:24 ` Eli Zaretskii
2020-08-03 14:36 ` Stefan Monnier
2020-08-08 18:13 ` Jonas Bernoulli
2020-08-08 21:59 ` Stefan Monnier
2020-08-09 8:37 ` Jonas Bernoulli
2020-08-03 3:16 ` Richard Stallman
2020-08-02 2:26 ` Richard Stallman
2020-08-08 12:02 ` Jonas Bernoulli
2020-08-08 18:37 ` Jonas Bernoulli
2020-08-08 18:58 ` Eli Zaretskii
2020-08-09 8:35 ` Jonas Bernoulli
2020-08-12 16:53 ` Thorsten Jolitz
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=jwvh7tujg4b.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=jonas@bernoul.li \
/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).