From: Alan Tyree <typhoon@aanet.com.au>
To: Steven Arntson <steven@stevenarntson.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Chapter headings
Date: Sat, 29 Mar 2014 12:52:31 +1100 [thread overview]
Message-ID: <CAGMsgMxPCe1ypjX9cCKaa+-UdbVYGWy9vtKk7FmFzaoRmY3hsg@mail.gmail.com> (raw)
In-Reply-To: <87ha6i82vd.fsf@stevenarntson.com>
[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]
Unless you have the structure of your book set in stone, numbers just get
in your way. The great power of org is being able to write 'modularly' and
rearrange at will.
When you export, your chapter/section numbers will be right as well as all
cross references.
I think you'll be happier to ignore numbered headings when writing. I've
just moved to org for a 600+ page book -- Magic (and even more magic once
the whole bibliographic reference problem is solved).
Cheers,
Alan
On 29 March 2014 07:49, Steven Arntson <steven@stevenarntson.com> wrote:
> Nick Dokos <ndokos@gmail.com> writes:
>
> > 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.
> >
> > Nick
>
> I'm just accustomed to seeing them in my working drafts. Perhaps it is I
> who needs to change, rather than my unnumbered chapters! Something I
> haven't explored yet with org-mode is exporting to LaTeX, but it sounds
> like these numbers can be made to appear after export. I'm not yet a
> LaTeX user, so I may wait to explore that until I get to it.
>
> Best!
> steven
>
>
>
>
--
Alan L Tyree http://www2.austlii.edu.au/~alan
Tel: 04 2748 6206
[-- Attachment #2: Type: text/html, Size: 1987 bytes --]
next prev parent reply other threads:[~2014-03-29 1:52 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 [this message]
2014-03-29 2:18 ` Steven Arntson
2014-03-29 13:30 ` Scott Randby
2014-03-31 8:06 ` Sebastien Vauban
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=CAGMsgMxPCe1ypjX9cCKaa+-UdbVYGWy9vtKk7FmFzaoRmY3hsg@mail.gmail.com \
--to=typhoon@aanet.com.au \
--cc=emacs-orgmode@gnu.org \
--cc=steven@stevenarntson.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/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).