emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: how to include graphics in pdf output
Date: Wed, 21 Mar 2012 05:39:40 -0500	[thread overview]
Message-ID: <CA+M2ft80Fcfri1HwDQRdOCtJ0NNtnep0BO43XX2A3Ja6KUK9aw@mail.gmail.com> (raw)
In-Reply-To: <804ntip9dv.fsf@somewhere.org>

On Wed, Mar 21, 2012 at 4:54 AM, Sebastien Vauban
<wxhgmqzgwmuf@spammotel.com> wrote:
> Hi Christopher,
> "Christopher W. Ryan" wrote:
>> However, in both cases, the inline tasks themselves also appear in the
>> final pdf. I was trying to avoid that, and I though todo:nil in
>> #+OPTIONS would accomplish that objective, but it did not.  Is there a
>> way to not export inline tasks?
>> Here are the modifications to the small reproducible file I started with:
>> #+OPTIONS:   todo:nil toc:nil tags:nil
>> #+LATEX_HEADER: \usepackage[margin=1in]{geometry}
>> #+LATEX_HEADER: \usepackage{graphicx}
>> * I guess I don't understand enough about Org's hierarchical trees yet
>> ** Study design
>> Here's what we'll do.
>> Blah blah blah
>> *************** TODO I'd like this not to appear in pdf
>> *************** END
>> So now this text here appears in the pdf, as desired. But I'd like the
>> inline task above not to appear in the pdf. I though todo:nil would
>> prevent it from appearing, but it did not.
> An inline task is almost a normal headline, hence you can put a tag such as
> "noexport" on it, and have the inline task not exported.


,----- M-x help RET v RET org-inlinetask-export -----
| org-inlinetask-export is a variable defined in `org-inlinetask.el'.
| Its value is t
| Documentation:
| Non-nil means export inline tasks.
| When nil, they will not be exported.
| You can customize this variable.

Best regards,

> Best regards,
>  Seb
> --
> Sebastien Vauban

  reply	other threads:[~2012-03-21 10:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cryan@binghamton.edu>
2012-03-19 19:20 ` how to include graphics in pdf output Christopher W. Ryan
2012-03-19 19:53   ` Nick Dokos
2012-03-19 23:32     ` suvayu ali
2012-03-19 23:48       ` Nick Dokos
2012-03-20  4:12         ` Christopher W. Ryan
2012-03-20  4:46           ` Nick Dokos
2012-03-21  2:59             ` Christopher W. Ryan
2012-03-21  9:54               ` Sebastien Vauban
2012-03-21 10:39                 ` John Hendy [this message]
2012-03-21 14:05                   ` Christopher W. Ryan

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:

  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=CA+M2ft80Fcfri1HwDQRdOCtJ0NNtnep0BO43XX2A3Ja6KUK9aw@mail.gmail.com \
    --to=jw.hendy@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=wxhgmqzgwmuf@spammotel.com \


* 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


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).