From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Chapter headings
Date: Mon, 31 Mar 2014 10:06:25 +0200 [thread overview]
Message-ID: <86eh1i23ni.fsf@somewhere.org> (raw)
In-Reply-To: 87ppl6dptx.fsf@alphaville.bos.redhat.com
Nick Dokos wrote:
> Steven Arntson <steven-9v/4WlS9d01uOnY4IQmrIgC/G2K4zDHf@public.gmane.org> writes:
>
>> Hello, I'm a beginning org-mode user.
>>
>> I'm writing a book with many chapters, each chapter as a top-level
>> header (*). Is there a way to assign chapter numbers automatically, such
>> that I might get a result along the lines of:
>>
>> * 1. This is a chapter containing thousands of words.
>>
>> * 2. This is the next chapter, with many words.
>>
>> * 3. And so on.
>
> There are probably many ways to do that, but I want to invert the
> question: *why* do you want chapter numbers in your org file?
> I would argue that they are a bad idea in the vast majority of cases.
Numbers can be nice be particularly nice when having some colleague (or
boss) on the phone asking you to fix the typo on the second paragraph of
page 12. When you tell them you don't see page numbers, they give you
the section number... and you've to ask for the title, not its number.
This is to say that numbers could be a positive feedback for the writer,
but they certainly would have to be overlays on the Org headings, not
saved with the file.
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2014-03-31 8:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 20:08 Chapter headings Steven Arntson
2014-03-28 20:35 ` Nick Dokos
2014-03-28 20:49 ` Steven Arntson
2014-03-29 1:52 ` Alan Tyree
2014-03-29 2:18 ` Steven Arntson
2014-03-29 13:30 ` Scott Randby
2014-03-31 8:06 ` Sebastien Vauban [this message]
2014-03-28 20:41 ` Scott Randby
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86eh1i23ni.fsf@somewhere.org \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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/org-mode.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).