From: "François Pinard" <pinard@iro.umontreal.ca>
To: emacs-orgmode@gnu.org
Subject: Spurious exporting of text before first header
Date: Tue, 24 Sep 2013 23:58:28 -0400 [thread overview]
Message-ID: <86mwn1a6xn.fsf@iro.umontreal.ca> (raw)
Hi, Org people.
This is an old annoyance of the Org exporter, yet I'm not sure what
would be its best resolution.
Whenever I use :export: tags on headers within an Org file, I expect
only those headers and their contents to be exported (to HTML in my
case), and almost nothing else, which I then consider private.
However, if I have text and other contents prior to the first header of
a file, those contents are indeed exported, while I would prefer not.
Of course, #+TITLE and some other directives prior to the first header
should be honored for their effect. One might surely debate on the best
way to handle #+INCLUDE directive.
I wish the above comments might generate either a correction in Org, or
an advice for me! :-)
François
P.S. Some might suggest me that I avoid text prior to the first header.
Surely, I have hundreds of Org files and for them all, have some
personal conventions for their format and structure. For regularity
reasons, I would much like to continue having private initial text.
next reply other threads:[~2013-09-25 3:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 3:58 François Pinard [this message]
2013-09-25 7:34 ` Spurious exporting of text before first header 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
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=86mwn1a6xn.fsf@iro.umontreal.ca \
--to=pinard@iro.umontreal.ca \
--cc=emacs-orgmode@gnu.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.