emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: how to include graphics in pdf output
Date: Wed, 21 Mar 2012 10:54:04 +0100	[thread overview]
Message-ID: <804ntip9dv.fsf@somewhere.org> (raw)
In-Reply-To: 4F6943FA.3060109@binghamton.edu

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.

Best regards,
  Seb

-- 
Sebastien Vauban

  reply	other threads:[~2012-03-21  9:54 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 [this message]
2012-03-21 10:39                 ` John Hendy
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:
  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=804ntip9dv.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).