From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Mark Edgington <edgimar@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Export: Override headline numbering via properties
Date: Mon, 13 May 2013 12:54:36 +0200 [thread overview]
Message-ID: <87hai7taj7.fsf@gmail.com> (raw)
In-Reply-To: <CAMsBe8oazb48QN+xF5H5E5cpRXB7-teKUeQhyc8nh708F96K+A@mail.gmail.com> (Mark Edgington's message of "Mon, 13 May 2013 05:42:52 -0400")
Hello,
Mark Edgington <edgimar@gmail.com> writes:
> A couple possible use-cases:
>
> 1. a document (or chapter of a document) where the first headline
> contains general "introduction" information explaining what the rest
> of the document (chapter) is about (similar to an abstract, but not
> identical -- something that might contain sub-headings, lists, tables,
> etc.), and the remainder of the document (chapter) is the "real"
> content of the document -- the place where you want the numbering to
> begin.
You can still number these parts manually with, e.g.,
#+latex: \section*{Introduction}
before the first section in your Org document.
> 2. a document where only one of the headlines and its child-headlines
> halfway through the document should be un-numbered (maybe they
> represent an "example docoument" embedded within an
> instruction-manual).
I may be wrong, but this sounds like a hypothetical use case to me.
Anyway, your patch will not work on back-ends that rely on Org to
compute section numbers (e.g., ascii, html...) because even if you
ignore numbering for a particular headline, it still adds up internally.
IOW, you also need to patch `org-export--collect-headline-numbering'.
But that's not quite it, yet. Some back-ends (e.g., html) use that
internal number as a unique identifier for the headline. Actually, the
"artificial restriction" you are talking about is a way to allow every
headline to be numbered in a unique way, even if that number doesn't
appear in the output.
Therefore, you need to generate a unique identifier for all headlines,
a function to return it, and modify each back-end accordingly. This is
obviously doable, but it cannot fit in a TINYPATCH.
Since I wouldn't use this, I can hardly judge, but I would appreciate
some feedback from other users before we go too far in the
implementation.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-05-13 10:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 3:07 [PATCH] Export: Override headline numbering via properties Mark Edgington
2013-05-13 6:18 ` Nicolas Goaziou
2013-05-13 9:42 ` Mark Edgington
2013-05-13 10:54 ` Nicolas Goaziou [this message]
2013-05-14 4:39 ` Mark Edgington
2013-05-17 3:19 ` Albert Z. Wang
2013-05-23 19:03 ` Nicolas Goaziou
2013-05-13 10:11 ` Mark Edgington
[not found] ` <CAJcAo8u+pAqwuPtRDpDaLc7QE_1BvR7MXchgZRQDLRAv_iQ2Wg@mail.gmail.com>
2013-05-13 10:08 ` Mark Edgington
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=87hai7taj7.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=edgimar@gmail.com \
--cc=emacs-orgmode@gnu.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).