From: Nicolas Goaziou <n.goaziou@gmail.com>
To: "François Pinard" <pinard@iro.umontreal.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: Spurious exporting of text before first header
Date: Thu, 26 Sep 2013 13:26:59 +0200 [thread overview]
Message-ID: <87d2nv3jss.fsf@gmail.com> (raw)
In-Reply-To: <86ioxo90rd.fsf@iro.umontreal.ca> ("François Pinard"'s message of "Wed, 25 Sep 2013 15:09:26 -0400")
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.
WDYT?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-09-26 11:26 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 [this message]
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
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=87d2nv3jss.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--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).