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 19:57:10 +0200 [thread overview]
Message-ID: <86y56jtqix.fsf@somewhere.org> (raw)
In-Reply-To: 87mwmz1un7.fsf@gmail.com
Hello Nicolas,
Nicolas Goaziou wrote:
> "Sebastien Vauban" writes:
>
>> Wouldn't it be worth to make such a filter officially present in Org, not
>> only for Beamer?
>
> Here we are.
>
> No it wouldn't. As I said, it's a kludge used as a workaround in
> Beamer-specific syntax because headlines, which are not blocks, can only be
> ended with another headline or the end of buffer. It's a specific solution
> for a local problem.
I understand it *is* needed for Beamer.
> These do not usually generalize very well. For example,
> visibility cycling isn't related anymore to sections in export output:
>
> * H1
> Section 1
> * Ignore me! :ignoreheading:
> Section 1 (continued)
> * H2
> Section 2
For me, visibility in the original Org buffer and sections in export output
are orthogonal things. They don't impact each other.
> You can achieve the same (and, apparently, you already do) with a simple
> hook, without extending Org syntax. I _really_ think that's better.
Yes, but that would solve the problem of having "preliminary" notes well or not
exported in the output, depending on the fact you tag the section or not. That
was what you said: there is no good solution between saying that preliminary
notes will always be exported (as François wished) or never, if we can't
customize that.
And that would be not only for me: by putting a hook locally, my file won't
produce the same output for all the other users. That was the point of having
it in Org, as it seems it is a common request.
That said, that's not something I need; so I don't mind that much.
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2013-09-26 17:57 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
2013-09-26 15:15 ` Nicolas Goaziou
2013-09-26 17:57 ` Sebastien Vauban [this message]
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=86y56jtqix.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).