From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Achim Gratz <Stromeko@NexGo.DE>
Cc: emacs-orgmode@gnu.org
Subject: Re: new exporter / org-element
Date: Thu, 25 Oct 2012 14:18:05 +0200 [thread overview]
Message-ID: <871ugmn3sy.fsf@gmail.com> (raw)
In-Reply-To: <loom.20121025T090949-963@post.gmane.org> (Achim Gratz's message of "Thu, 25 Oct 2012 07:14:30 +0000 (UTC)")
Hello,
Achim Gratz <Stromeko@NexGo.DE> writes:
> Nicolas Goaziou <n.goaziou <at> gmail.com> writes:
>> > the pagebreak does not get exported to LaTeX since the Footnotes section
>> > will not be exported and the pagebreak is interpreted as being part of
>> > that section. It would be nice if there was a way to "bind" it to the
>> > following heading or alternatively move it past the heading but have it
>> > export before. Is that possible already or can it be implemented?
>>
>> Can't you move footnotes section at the end of your document instead?
>
> Yes, that's exactly the workaround I used.
Better: you can move the pagebreak just /above/ the footnote section, as
if the section didn't exist.
> But I think that there may be a general need to be able to wrap some
> code around an element on exporting (let's say, putting a table or
> section into a minipage) or prefix the export with something (like the
> pagebreak example) and have that code properly be part of the element.
> Note that we already have that functionality, sort of, for the title
> element of the export.
There's already such a mechanism: it's called "filters". I'm just
pointing out that, in your situation, it's not worth relying on this
kind of tool.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2012-10-25 12:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 18:54 new exporter / org-element Achim Gratz
2012-10-24 20:39 ` Nicolas Goaziou
2012-10-25 7:14 ` Achim Gratz
2012-10-25 12:18 ` Nicolas Goaziou [this message]
2012-10-25 19:53 ` Achim Gratz
2012-10-25 20:37 ` 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=871ugmn3sy.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=Stromeko@NexGo.DE \
--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).