emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Christopher W. Ryan" <cryan@binghamton.edu>
To: emacs-orgmode@gnu.org
Subject: Re: how to include graphics in pdf output
Date: Tue, 20 Mar 2012 22:59:06 -0400	[thread overview]
Message-ID: <4F6943FA.3060109@binghamton.edu> (raw)
In-Reply-To: <23599.1332218797@alphaville>



Nick Dokos wrote:
> 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


Well, I'm making some progress.

org-inlinetask-min-level = 15

I had previousl simply typed in an arbitrary number of stars by hand, 
for my inline tasks. If I use C-c C-x t to insert one, then figures and 
text subsequent to it do appear in the final pdf as desired.  If I type 
in 15 stars by hand, emacs recognizes this also as an inline task 
(judging by the syntax highlighting) and figures following it are again 
exported correctly.

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.


*************** TODO figure will follow this todo
*************** END
This line appears in the pdf too. Unfortunately, so does the inline task 
above it.

And the image shows up; its first appearance.


#+CAPTION: foo
#+LABEL:   foo
[[./DataLoggerImage.jpg]]

** But if I start a new 2-star heading

and put the image here, it works fine.  Second appearance of the image.

#+CAPTION: bar
#+LABEL:   bar
[[./DataLoggerImage.jpg]]


*************** TODO entered via C-c C-x t
*************** END

************** TODO just 14 stars typed by hand, and a figure after
                this should be the third figure in the pdf
                figure doesn't appear, nor does this text
************** END

#+CAPTION: bar
#+LABEL:   bar
[[./DataLoggerImage.jpg]]



Thanks.
--Chris

  reply	other threads:[~2012-03-21  2:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cryan@binghamton.edu>
2012-03-19 19:20 ` 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 [this message]
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=4F6943FA.3060109@binghamton.edu \
    --to=cryan@binghamton.edu \
    --cc=emacs-orgmode@gnu.org \
    --subject='Re: how to include graphics in pdf output' \
    /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

Code repositories for project(s) associated with this 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).