From: Detlef Steuer <email@example.com>
Subject: Re: [PATCH] Improve documentation of #+startup keyword
Date: Mon, 26 Apr 2021 10:04:37 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Am Mon, 26 Apr 2021 09:45:36 +0200
schrieb Bastien <email@example.com>:
> > I think that this would be a good addition to the manual, and help
> > clarify the behaviour --- so I've prepared a little patch to the
> > manual.
> Thanks for the patch. I think it better belongs to a worg page, as we
> try to avoid overloading the quite-already-big manual. Can you make
> this a contribution to Worg?
I really would like to have as much as possible in the manual.
My guess is, nobody prints it anymore, so the old concers about thick
manuals are irrelevant today.
If I must start looking through worg to find some information, my chance
of finding it has already halfed. :-)
Just my 2c
next prev parent reply other threads:[~2021-04-26 8:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 12:03 [PATCH] Improve documentation of #+startup keyword Timothy
2021-04-26 7:45 ` Bastien
2021-04-26 8:04 ` Detlef Steuer [this message]
2021-04-26 8:21 ` Bastien
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).