emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: Andrey Yankin <yankin013@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: LaTeX export. Substitute some headlines with arbitrary command
Date: Thu, 14 Mar 2013 02:17:38 -0400	[thread overview]
Message-ID: <13742.1363241858@alphaville> (raw)
In-Reply-To: Message from Andrey Yankin <yankin013@gmail.com> of "Thu\, 14 Mar 2013 09\:14\:07 +0400." <CANxQ4Z2Fmd9o2ez+cd66pAtiMxrLrjhFBRmok55LGZa9MEnWAw@mail.gmail.com>

Andrey Yankin <yankin013@gmail.com> wrote:

> Sorry if it wasn't clear.
> I should have illustrate this.
> 
> Input:
> 
> * Headline 1
> ** Node 1.1
>   Content 1
> * Headline 2
>   Content 2
> * Headline 3
>   Content 3
> * Headline 4
>   Content 4
> * Headline 5
>   Content 5
> 
> Desired output:
> 
> \intro
> \subsection{Node 1.1}
>   Content 1
> \section{Headline 2}
>   Content 2
> \section{Headline 3}
>   Content 3
> \section{Headline 4}
>   Content 4
> \conclusion
>   Content 5
> 
> First and fifth top headlines output is replaced. And others are defaults.
> All children keep the same.
> 

OK - I don't think you can do this with org-latex-classes: there is no
provision for exceptional cases there. Charles Berry suggested filters:
maybe something can be done with that.

FWIW, I would just wait until the last minute and then when it's time to
produce the final pdf, I'd replace the two headlines by hand - but that
assumes that the document is a one-off, do-it-once-and-never-again kind
of thing.

Nick

> 2013/3/14 Nick Dokos <nicholas.dokos@hp.com>
> 
>     Andrey Yankin <yankin013@gmail.com> wrote:
>    
>     > Hi!
>     >
>     > I want arbitrary top level headline to be exported not as \section (or whatever it is) but
>     with some
>     > other arbitrary latex command.
>     >
>     > I even do not want to use headline text. Just write \intro instead of \section{...} in tex
>     file.
>     >
>     > I've tried some fiddling with :noexport: and :export: tags to hide output for selected
>     headlines. It
>     > didn't work.
>     >
>     > Currently I'm heading to this metod: http://stackoverflow.com/a/9679105 of creating my own
>     parser.
>     >
>     > Are there any easier solutions?
>     >
>    
>     Have you tried customizing the org-latex-classes variable? I'm not quite
>     sure what you are trying to do (an example would help), but I don't see
>     any obstacles.
>    
>     Nick
> 
> 
> ----------------------------------------------------
> Alternatives:
> 
> ----------------------------------------------------

  reply	other threads:[~2013-03-14  6:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-13 20:50 LaTeX export. Substitute some headlines with arbitrary command Andrey Yankin
2013-03-13 22:49 ` Charles Berry
2013-03-14  0:14 ` Nick Dokos
2013-03-14  5:14   ` Andrey Yankin
2013-03-14  6:17     ` Nick Dokos [this message]
2013-03-14  8:07       ` Andrey Yankin

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=13742.1363241858@alphaville \
    --to=nicholas.dokos@hp.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yankin013@gmail.com \
    /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).