From: suvayu ali <fatkasuvayu+linux@gmail.com>
To: Indraneel Majumdar <indraneel@indraneel.info>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: Omit top level heading in latex export?
Date: Sun, 3 Oct 2010 09:05:44 -0700 [thread overview]
Message-ID: <AANLkTimr5mYemXoxCFAoNLVcgV_hWg-w231m1+GRqFtz@mail.gmail.com> (raw)
In-Reply-To: <4CA8A5F9.5070301@indraneel.info>
On 3 October 2010 08:49, Indraneel Majumdar <indraneel@indraneel.info> wrote:
>
>
> On 2010-10-03 21:12, suvayu ali wrote:
>>
>> On 3 October 2010 08:31, Indraneel Majumdar<indraneel@indraneel.info>
>> wrote:
>>>
>>> On 2010-10-03 20:57, suvayu ali wrote:
>>>>
>>>> On 3 October 2010 06:31, Indraneel Majumdar<indraneel@indraneel.info>
>>>> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I'm running into a problem with latex export. I have several essays
>>>>> under
>>>>> a
>>>>> top level heading "Essays". How can I export say only one essay without
>>>>> the
>>>>> top level heading "Essays" also showing up in the output as a
>>>>> "Section"?
>>>>> I
>>>>> want the heading of my essay to be displayed as a latex section. Is
>>>>> this
>>>>> possible in any simple way? The manual describes some option to define
>>>>> my
>>>>> own class in the .emacs file, but I couldn't understand that very well.
>>>>> eg.
>>>>>
>>>>> * Essays
>>>>> ** Essay One
>>>>> ** Essay Two
>>>>>
>>>>> I want to export only "Essay Two" (eg with a :export: tag) and don't
>>>>> want
>>>>> "Essays" to show up.
>>>>>
>>>> What about just exporting the subtree you want? I believe the way to
>>>> do that is to go to the subtree and while exporting limit the export
>>>> with `1'. Hope this helps.
>>>>
>>> Yes, that exports the subtree (Essay Two) and also exports "Essays" (but
>>> not
>>> "Essay One"). I do not want "Essays" to show up at all.
>>>
>> In that case you can try the `noexport' tag on the top level headline
>> with this header `#+EXPORT_EXCLUDE_TAGS: noexport' option. I just
>> tried it, seems to work pretty well.
>>
> Does not work for me. It blocks out the entire tree, even if I have :export:
> on "Essay Two". From the manual, it seems that is how it should be.
Could be a result of some setting in my setup. Only remotely relevant
variable I could find was `(setq org-hierarchical-todo-statistics
nil)'. I don't usually export my trees except for beamer
presentations. Not sure what else you could try. Sorry. :(
>>>
>>> Indraneel
>
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2010-10-03 16:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-03 13:31 Omit top level heading in latex export? Indraneel Majumdar
2010-10-03 15:27 ` suvayu ali
2010-10-03 15:31 ` Indraneel Majumdar
2010-10-03 15:42 ` suvayu ali
2010-10-03 15:49 ` Indraneel Majumdar
2010-10-03 16:05 ` suvayu ali [this message]
2010-10-03 16:51 ` Matt Lundin
2010-10-03 17:31 ` Indraneel Majumdar
2010-10-03 18:18 ` Indraneel Majumdar
2010-10-25 20:49 ` Hsiu-Khuern Tang
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=AANLkTimr5mYemXoxCFAoNLVcgV_hWg-w231m1+GRqFtz@mail.gmail.com \
--to=fatkasuvayu+linux@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=indraneel@indraneel.info \
/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).