From: Carsten Dominik <carsten.dominik@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: "François Pinard" <pinard@iro.umontreal.ca>, emacs-orgmode@gnu.org
Subject: Re: Spurious exporting of text before first header
Date: Thu, 26 Sep 2013 22:46:30 +0200 [thread overview]
Message-ID: <F4C998D0-3957-4C02-AD73-428B40AE730B@gmail.com> (raw)
In-Reply-To: <87d2nv3jss.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1657 bytes --]
On 26.9.2013, at 13:26, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
> Hello,
>
> François Pinard <pinard@iro.umontreal.ca> writes:
>
>> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>>
>>> François Pinard <pinard@iro.umontreal.ca> writes:
>>
>>>> The spirit behind :export: is [...]
>>
>>> I agree, this is a misfeature. This should be fixed in master. Thank
>>> you for bringing it out.
>>
>> Thanks as well. :-)
>
> OTOH, this "fix" introduces another problem.
>
> 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. IOW, it is easier to make that text disappear than to make it
> appear.
>
> IOW, even though the new behaviour is more logical, in the end, I'm not
> sure it is desirable. It's the old "good" versus "best" story.
The new behavior is the correct one. :export: selects stuff to be exported.
A way to have initial text and some trees would be to add :noexport: to the
ones that should not be exported.
If there is string desire to be able to export initial text with :export: tags,
the only solutions I see would be an additional variable with an #+OPTIONS
equivalent, like org-export-force-initial-content. Default obviously off,
setting the variable to t with list or customize not recommended, but
possible to set it on a per file basis with #+OPTIONS
- Carsten
>
> WDYT?
>
>
> Regards,
>
> --
> Nicolas Goaziou
>
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2013-09-26 20:46 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
2013-09-26 20:46 ` Carsten Dominik [this message]
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=F4C998D0-3957-4C02-AD73-428B40AE730B@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
--cc=pinard@iro.umontreal.ca \
/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).