From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Christopher W. Ryan" Subject: Re: how to include graphics in pdf output Date: Tue, 20 Mar 2012 22:59:06 -0400 Message-ID: <4F6943FA.3060109@binghamton.edu> References: <4F6786E5.5030108@binghamton.edu> <5734.1332186799@alphaville> <12681.1332200900@alphaville> <4F68039B.3010208@binghamton.edu> <23599.1332218797@alphaville> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:32769) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SABlc-000299-Mg for emacs-orgmode@gnu.org; Tue, 20 Mar 2012 22:59:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SABlV-0005wk-V3 for emacs-orgmode@gnu.org; Tue, 20 Mar 2012 22:59:16 -0400 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.122]:9473) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SABlV-0005wE-Pc for emacs-orgmode@gnu.org; Tue, 20 Mar 2012 22:59:09 -0400 In-Reply-To: <23599.1332218797@alphaville> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Nick Dokos wrote: > Christopher W. Ryan 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