From: Alan L Tyree <alantyree@gmail.com>
To: Rasmus <rasmus@gmx.us>, emacs-orgmode@gnu.org
Cc: tsd@tsdye.com
Subject: Re: [patch, ox] Unnumbered headlines
Date: Sun, 21 Sep 2014 06:34:14 +1000 [thread overview]
Message-ID: <541DE4C6.8040402@gmail.com> (raw)
In-Reply-To: <87k34y701i.fsf@gmx.us>
Thanks very much for working on this, Rasmus. I'll try to test it out
over the next couple of days. It really will make book production much
nicer!
Cheers,
Alan
On 21/09/14 02:02, Rasmus wrote:
> Hi,
>
> I'm happy to finally be able to send an updated version of this patch
> that touches most backends in lisp/, but not the manual. I have been
> moving over the summer etc.
>
> You now specify unnumbered headlines with properties. I think this is
> better since being unnumbered it's a pretty permanent state. It's
> pretty hard to discover though, other than by looking at the output.
>
> So this works as expected:
>
> * Some headline
> :PROPERTIES:
> :UNNUMBERED: t
> :END:
>
> There's no :NUMBERED property and :UNNUMBERED is hardcoded.
>
> I introduce a new function `org-export-get-headline-id` which returns
> the first non-nil from the following list. There's a caveat:
> CUSTOM_ID is ensured to be unique! Did I open the famous can of worm?
>
> 1. The CUSTOM_ID property.
> 2. A relative level number if the headline is numbered.
> 3. The ID property
> 4. A new generated unique ID.
>
> Anyhow, `org-export-get-headline-id' ensures that we can refer to
> unnumbered headlines, which was not possible before. Of course, in
> LaTeX such ref to a \section* will be nonsense, so we could introduce
> a \pageref here. I'm unsure about whether this conflicts
> `org-latex-custom-id-as-label' which I had never seen until today
> (also notes on this in patch).
>
> I have updated backends in lisp/, but I'm at most(!) an "expert" on
> LaTeX. However, I have tested all backends to the best of my ability.
>
> Please feel free to test and let me know about any discrepancies!
>
> Cheers,
> Rasmus
>
> PS: Not knowing or caring much about md, the links generated by it to
> headlines seem wrong. Referring to headline 1 it only prints "1".
> Should it be something like "[LABEL](1)"?
>
>
--
Alan L Tyree http://www2.austlii.edu.au/~alan
Tel: 04 2748 6206 sip:typhoon@iptel.org
next prev parent reply other threads:[~2014-09-20 20:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 13:39 [patch, ox] Unnumbered headlines Rasmus
2014-08-08 22:35 ` Alan L Tyree
2014-08-09 1:04 ` [patch, ox] Unnumbered headlines - early test Alan L Tyree
2014-08-09 7:47 ` [patch, ox] Unnumbered headlines Detlef Steuer
2014-08-11 14:18 ` Nicolas Goaziou
2014-08-11 15:37 ` Rasmus
2014-08-12 8:58 ` Nicolas Goaziou
2014-09-20 16:02 ` Rasmus
2014-09-20 20:34 ` Alan L Tyree [this message]
2014-09-21 13:12 ` Nicolas Goaziou
2014-09-21 14:37 ` Rasmus
2014-09-21 19:40 ` Nicolas Goaziou
2014-09-21 20:13 ` Rasmus
2014-09-22 15:53 ` Nicolas Goaziou
2014-09-23 0:35 ` Rasmus
2014-09-23 1:10 ` Thomas S. Dye
2014-09-26 7:51 ` Nicolas Goaziou
2014-09-26 13:48 ` Rasmus
2014-09-27 8:19 ` Nicolas Goaziou
2014-09-30 22:54 ` Rasmus
2014-10-02 0:35 ` Rasmus
2014-10-03 7:56 ` Nicolas Goaziou
2014-10-03 8:49 ` Sebastien Vauban
2014-10-03 10:26 ` Rasmus
2014-10-03 20:14 ` Nicolas Goaziou
2014-10-03 20:31 ` Rasmus
2014-10-05 8:06 ` Nicolas Goaziou
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=541DE4C6.8040402@gmail.com \
--to=alantyree@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
--cc=tsd@tsdye.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).