emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: latex export of #+header: lines
Date: Tue, 17 Jan 2012 12:27:06 +0100	[thread overview]
Message-ID: <87ty3uwovp.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: 80k44q4scz.fsf@somewhere.org

"Sebastien Vauban"
<wxhgmqzgwmuf@spammotel.com> writes:


> Hi Andreas,
>
> Andreas Leha wrote:
>> I am experiencing a problem with the latex exporter:  #+header: lines
>> are visible in the exported file.
>>
>> Example:
>>
>> /==================================================\
>> * test header tag                                 
>>   #+caption: foo                                  
>>   #+label: fig:fig1                               
>>   #+name: foo                                     
>>   #+header: :file foo.png                         
>>   #+header: :width 3600 :height 3600 :res 600     
>>   #+begin_src R :exports results :results graphics
>>     plot(1:10, 1:10)                              
>>   #+end_src                                       
>> \==================================================/
>
> Try using #+LaTeX_HEADER: lines, instead.
>
> Best regards,
>   Seb


Hi Seb,

thanks for the reply!

But as far as I know, #+LaTeX_HEADER (as described
here http://orgmode.org/org.html#Header-and-sectioning) is a different
thing from babel source block header arguments (as described here
http://orgmode.org/org.html#Code-block-specific-header-arguments)

I use both quite extensively.

The #+header: tags can be avoided by creating loooong #+begin_src
lines.  But still, they should not appear in the exported tex code, I
think.

Best,
Andreas

next prev parent reply	other threads:[~2012-01-17 11:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-17  8:31 latex export of #+header: lines Andreas Leha
2012-01-17  8:59 ` Sebastien Vauban
2012-01-17 11:27   ` Andreas Leha [this message]
2012-01-17 11:30     ` Andreas Leha
2012-01-17 12:51       ` Sebastien Vauban
2012-01-17 12:52       ` Eric S Fraga
2012-01-19 20:09       ` Jambunathan K
2012-01-21  0:19         ` Andreas Leha
2012-01-24 15:01         ` Bastien

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=87ty3uwovp.fsf@med.uni-goettingen.de \
    --to=andreas.leha@med.uni-goettingen.de \
    --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

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).