all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Sebastien Vauban
	<public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: Spurious exporting of text before first header
Date: Thu, 26 Sep 2013 17:15:40 +0200	[thread overview]
Message-ID: <87mwmz1un7.fsf@gmail.com> (raw)
In-Reply-To: <86eh8bmylt.fsf@somewhere.org> (Sebastien Vauban's message of "Thu, 26 Sep 2013 16:44:30 +0200")



"Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
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. 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

You can achieve the same (and, apparently, you already do) with a simple
hook, without extending Org syntax. I _really_ think that's better.


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2013-09-26 15:16 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mwmz1un7.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
    --cc=public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.