From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: proposal to have ignoreheading tags/properties
Date: Fri, 13 Jun 2014 16:32:34 +0200 [thread overview]
Message-ID: <87oaxwvq0t.fsf@gmx.us> (raw)
In-Reply-To: 87fvja576z.fsf@gmail.com
Thorsten Jolitz <tjolitz@gmail.com> writes:
> Ken Mankoff <mankoff@gmail.com> writes:
>
>> Another common (for me) example is to have a heading called "* Appendix"
>> in a paper, and then the LaTeX "\appendix" command. The Org heading is
>> just for me. It should not be exported. All headings below the \appendix
>> command are Org sub-sections but should be promoted to \section in the
>> final document.
>
> then IMO it should be
>
> ,----------------------------
> | * Appendix
> | ** Latex Command :noexport:
> | \appendix
> | ** Subsec1
> | ** Subsec2 ...
> `----------------------------
Your code example is broken, but let's not care about that for now.
So the appendix case is kind of special. Really what we want is to
inject a command before the insertion of the appendix. Due to the
nature of LaTeX this is easy. I often do something like
* appendix pre :ignoreheading:
#+LATEX: \appendix
* my appendix
content
However, perhaps a property specifying a command to be inserted before
the headline is more appropriate. Then, we could write the above as
* my appendix
:PROPERTIES:
:LATEX_PRE_HEADING: \appendix
:HTML_PRE_HEADING: <appendix>
:HTML_POST_HEADING: </appendix>
:END:
content
which would export
\appendix
\section{my appendix}
content
Of course, in the above example it would be better to set the property
HTML_CONTAINER to appendix for html export.
—Rasmus
--
Together we'll stand, divided we'll fall
next prev parent reply other threads:[~2014-06-13 14:30 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 16:49 proposal to have ignoreheading tags/properties Mark Edgington
2014-06-12 17:32 ` Thorsten Jolitz
2014-06-12 17:41 ` Ken Mankoff
2014-06-12 18:11 ` Thorsten Jolitz
2014-06-12 18:16 ` Ken Mankoff
2014-06-13 14:32 ` Rasmus [this message]
2014-06-13 15:02 ` Thorsten Jolitz
2014-06-12 18:09 ` Mark Edgington
2014-06-12 18:12 ` Eric Schulte
2014-06-12 18:54 ` Aaron Ecay
2014-06-12 19:21 ` Nicolas Girard
2014-06-12 19:26 ` Ken Mankoff
2014-06-12 19:52 ` Nicolas Girard
2014-06-13 1:20 ` Samuel Wales
2014-06-12 19:34 ` Nicolas Girard
2014-06-12 20:13 ` Eric Schulte
2014-06-12 22:42 ` Nicolas Girard
2014-06-12 23:36 ` Eric Schulte
2014-06-13 0:35 ` Ken Mankoff
2014-06-13 0:46 ` Eric Schulte
2014-06-13 2:35 ` Ken Mankoff
2014-06-13 11:11 ` Eric Schulte
2014-06-13 3:28 ` Mark Edgington
2014-06-13 14:23 ` Rasmus
2014-06-14 12:43 ` Nicolas Goaziou
2014-06-14 16:48 ` Mark Edgington
2014-06-14 18:12 ` Aaron Ecay
2014-06-14 18:12 ` Nicolas Goaziou
2014-06-14 18:07 ` Aaron Ecay
2014-06-14 18:22 ` Nicolas Goaziou
2014-06-14 22:39 ` Aaron Ecay
2014-06-16 1:14 ` Eric Schulte
2014-06-16 8:08 ` Nicolas Goaziou
2014-06-16 12:19 ` Mark Edgington
2014-06-16 13:29 ` Eric Schulte
2014-06-22 2:03 ` Aaron Ecay
2014-06-22 23:52 ` Eric Schulte
2014-07-27 17:21 ` Bastien
2014-07-28 18:15 ` Mark Edgington
2014-07-28 18:27 ` Rasmus
2014-07-28 19:21 ` Mark Edgington
2014-07-28 19:43 ` Nicolas Goaziou
2014-07-28 22:01 ` Rasmus
2014-07-29 14:31 ` Bastien
2014-08-02 5:16 ` Mark Edgington
2014-08-06 4:09 ` Aaron Ecay
2014-06-13 2:38 ` Eric Abrahamsen
2014-06-13 4:07 ` Mark Edgington
2014-06-13 4:44 ` Eric Abrahamsen
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=87oaxwvq0t.fsf@gmx.us \
--to=rasmus@gmx.us \
--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 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).