From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Mark Meyer <mark@ofosos.org>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Searching for a headline
Date: Sun, 26 Feb 2017 19:12:10 +0100 [thread overview]
Message-ID: <87wpcces91.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <573a07d1-1d0f-20e0-fc52-eadf5f46955d@ofosos.org> (Mark Meyer's message of "Sun, 26 Feb 2017 18:54:59 +0100")
Mark Meyer <mark@ofosos.org> writes:
> On 02/26/17 18:28, Nicolas Goaziou wrote:
> I wrote it yesterday, the code's up at
>
> https://github.com/ofosos/org-epub
Great.
> it's a little crufty, because I did write it for org 8 initially.
>
> Hmm, I have to think about it. I would like to either have a 1:1 mapping
> between the elements `org-element' delvers and the links the export
> backend generates or create a function that runs before the export that
> generates :custom_id properties for every element that doesn't have
> one.
Did you look at `org-html--format-toc-headline'?
Also, if you want to collect headlines above a given level, there is
`org-export-collect-headlines'.
> This was easier in org 8, since every internal link was just something
> like `sec-8-2'.
It is also easy in Org 9 : (org-export-get-reference headline info). See
its use in the function above.
Regards,
next prev parent reply other threads:[~2017-02-26 18:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-26 13:41 Searching for a headline Mark Meyer
2017-02-26 15:27 ` Nicolas Goaziou
2017-02-26 16:11 ` Mark Meyer
2017-02-26 16:39 ` Nicolas Goaziou
2017-02-26 16:58 ` Mark Meyer
2017-02-26 17:28 ` Nicolas Goaziou
2017-02-26 17:54 ` Mark Meyer
2017-02-26 18:12 ` Nicolas Goaziou [this message]
2017-02-26 18:21 ` Mark Meyer
2017-02-26 18:28 ` Nicolas Goaziou
2017-02-26 18:30 ` Mark Meyer
2017-02-26 21:46 ` Mark Meyer
2017-02-26 19:32 ` Eric Abrahamsen
2017-02-26 20:40 ` Mark Meyer
2017-02-26 21:34 ` Eric Abrahamsen
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=87wpcces91.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=mark@ofosos.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).