John Hendy wrote: > On Wed, Mar 21, 2012 at 4:54 AM, Sebastien Vauban > <wxhgmqzgw...@spammotel.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. > > Also, > > ,----- 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, > John > > >> >> Best regards, >> Seb >> >> -- >> Sebastien Vauban >> >> > Excellent! Thanks everyone. --Chris Christopher W. Ryan, MD SUNY Upstate Medical University Clinical Campus at Binghamton 425 Robinson Street, Binghamton, NY 13904 cryanatbinghamtondotedu "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."]
