From: "Christopher W. Ryan" <email@example.com>
Subject: Re: how to include graphics in pdf output
Date: Wed, 21 Mar 2012 10:05:06 -0400 [thread overview]
Message-ID: <4F69E012.firstname.lastname@example.org> (raw)
John Hendy wrote:
> On Wed, Mar 21, 2012 at 4:54 AM, Sebastien Vauban
> <email@example.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?
>> 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,
>> Sebastien Vauban
Excellent! Thanks everyone.
Christopher W. Ryan, MD
SUNY Upstate Medical University Clinical Campus at Binghamton
425 Robinson Street, Binghamton, NY 13904
"Observation is a more powerful force than you could possibly reckon.
The invisible, the overlooked, and the unobserved are the most in danger
of reaching the end of the spectrum. They lose the last of their light.
From there, anything can happen . . ." [God, in "Joan of Arcadia,"
episode entitled, "The Uncertainty Principle."]
prev parent reply other threads:[~2012-03-21 14:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <firstname.lastname@example.org>
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
2012-03-21 14:05 ` Christopher W. Ryan [this message]
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 \
* 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).