From: Nick Dokos <nicholas.dokos@hp.com>
To: "Christopher W. Ryan" <cryan@binghamton.edu>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: how to include graphics in pdf output
Date: Tue, 20 Mar 2012 00:46:37 -0400 [thread overview]
Message-ID: <23599.1332218797@alphaville> (raw)
In-Reply-To: Message from "Christopher W. Ryan" <cryan@binghamton.edu> of "Tue, 20 Mar 2012 00:12:11 EDT." <4F68039B.3010208@binghamton.edu>
Christopher W. Ryan <cryan@binghamton.edu> wrote:
> I've attached a small org file that reproduces my problem with getting
> images to export to pdf. I've also attached the resulting .tex file.
>
> I think my issue may have something to do with my misunderstanding of
> inline tasks, since if I put my org code for inclusion of the image
> elsewhere in the org file, under its own 2nd level heading (2 stars)
> then it exports fine. The narrative text in the attached org file
> explains my observations in more detail.
>
> #+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.
>
> As patients of home care agencies, the subjects will all be considered homebound by definition. Subjects with cognitive impairment or psychiatric illness sufficiently severe to make them unable to consent to the study will not be eligible.
> ****** TODO notice how "end" on next line is expandable
> ****** END
> Somehow this text is under, hierarchically-speaking, the END statement of this inline task.
>
> So it does not show up in the final pdf
>
> ****** TODO there is text >>and the image file<< inside "end"
> ****** END
>
> Neither does this paragraph.
>
> Neither does this image, which must also be under the END statement of the inline task
>
> #+CAPTION: Temperature and humidity data logger
> #+LABEL: datalogger
> [[./DataLoggerImage.jpg]]
>
> ** But if I start a new 2-star heading
>
> and put the image here, it works fine.
>
> #+CAPTION: Temperature and humidity data logger
> #+LABEL: datalogger
> [[./DataLoggerImage.jpg]]
>
What is the value of org-inlinetask-min-level? If it's the default 15,
then you just haven't formatted the inline tasks correctly (not enough
stars)- did you use C-c C-x t to insert them? I used that to
insert the inline tasks and I got the following org file which exports
correctly afaict:
--8<---------------cut here---------------start------------->8---
#+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.
As patients of home care agencies, the subjects will all be considered homebound by definition. Subjects with cognitive impairment or psychiatric illness sufficiently severe to make them unable to consent to the study will not be eligible.
*************** TODO notice how "end" on next line is expandable
*************** END
Somehow this text is under, hierarchically-speaking, the END statement of this inline task.
So it does not show up in the final pdf
*************** TODO there is text >>and the image file<< inside "end"
*************** END
Neither does this paragraph.
Neither does this image, which must also be under the END statement of the inline task
#+CAPTION: foo
#+LABEL: foo
[[./DataLoggerImage.jpg]]
** But if I start a new 2-star heading
and put the image here, it works fine.
#+CAPTION: bar
#+LABEL: bar
[[./DataLoggerImage.jpg]]
--8<---------------cut here---------------end--------------->8---
Nick
next prev parent reply other threads:[~2012-03-20 4:46 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 [this message]
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
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=23599.1332218797@alphaville \
--to=nicholas.dokos@hp.com \
--cc=cryan@binghamton.edu \
--cc=emacs-orgmode@gnu.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).