From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Spurious exporting of text before first header
Date: Thu, 26 Sep 2013 16:44:30 +0200 [thread overview]
Message-ID: <86eh8bmylt.fsf@somewhere.org> (raw)
In-Reply-To: 87r4cb1wgi.fsf@gmail.com
Hello Nicolas,
Nicolas Goaziou wrote:
> "Sebastien Vauban" writes:
>> Nicolas Goaziou wrote:
>>
>>> What if a user wants to both use :export: tag and export text before
>>> first headline? An almost equivalent solution for him would be to add
>>> a headline before that text and append it an :export: tag. But in that
>>> case, he will get the additional headline in the output, which isn't
>>> desirable.
>>
>> He would have to add as well the tag ":ignoreheading:", right, and would
>> have no problem in the output?
>
> AFAIK, there is no such thing as a :ignoreheading: tag, at least not in the
> general case (Beamer export back-end has this feature, but it's a kludge).
> You may be referring to a personal export filter.
Entirely possible: I've seen that while reading posts of this ML.
Wouldn't it be worth to make such a filter officially present in Org, not only
for Beamer?
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2013-09-26 14:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 3:58 Spurious exporting of text before first header François Pinard
2013-09-25 7:34 ` Sebastien Vauban
2013-09-25 15:03 ` François Pinard
2013-09-25 17:25 ` Nicolas Goaziou
2013-09-25 19:09 ` François Pinard
2013-09-26 11:26 ` Nicolas Goaziou
2013-09-26 11:38 ` Sebastien Vauban
2013-09-26 14:36 ` Nicolas Goaziou
2013-09-26 14:44 ` Sebastien Vauban [this message]
2013-09-26 15:15 ` Nicolas Goaziou
2013-09-26 17:57 ` Sebastien Vauban
2013-09-26 20:46 ` Carsten Dominik
2013-09-26 8:53 ` Marcin Borkowski
2013-09-25 19:05 ` François Pinard
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=86eh8bmylt.fsf@somewhere.org \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).