Re: [Orgmode] Latex Export

[Russell Adams]

On a note related to #+OPTIONS and exporting, I've taken to using
sub-buffers (C-c C-x b) on a tree to limit my view to a specific
tree. I've discovered that I can export in this mode, however, export
doesn't honor the #+OPTIONS from the original file.

I'm sure this is because the exporter is limiting its scope to the
current buffer, as if I paste my #+OPTIONS at the top of the subtree
buffer, it works fine. This is only temporary though, and doesn't
survive reopening the subbuffer, and adds the text to the prior
heading's content. ;]

Other than temporarily adding an OPTIONS line, what are my options? I
don't recall export options as a property yet. I suppose I could set
common options in my .emacs.

I welcome comments!

Thanks!

On Sun, Dec 02, 2007 at 09:44:33PM +0000, Bastien wrote:
> Hi Russell,
> 
> Russell Adams <address@hidden> writes:
> 
> > The exporters all refuse to export text before the first headline. I
> > agree with that.
> 
> The exporters skip text before the first headline only if you set the
> relevant option:
> 
> #+OPTIONS: skip:t
> 
> If you don't specify anything about this in the #+OPTIONS line, then the
> exporters will fall back on `org-export-skip-text-before-1st-heading'.
> 
> This applies to normal text as well as text inside #+BEGIN_LaTeX and
> #+END_LaTeX markers.
> 
> But this does not apply to text after #+TEXT though.  This text is
> *always* exported.
> 
> > However I'm including per buffer options at the top of my file,
> > #+OPTIONS and the like. Turns out that #+BEGIN_LaTeX and #+END_LaTeX
> > before the first headline are considered comments and not exported.
> >
> > This is a problem where I'm trying to select a style or define
> > variables used later in LaTeX code.
> 
> I think the right way to do this is to set a local value for the
> variable `org-export-latex-append-header' at the end of your file:
> 
> ,----
> | * COMMENT LaTeX local variable
> | 
> | # Local Variables:
> | # org-export-latex-append-header: "\\usepackage{fancyhrd}"
> | # End:
> `----
> 
> This will append "\usepackage{fancyhrd}" to the LaTeX header that is
> defined in `org-export-latex-classes'.
> 
> > I think that BEGIN/END latex should be considered configuration data
> > like other /^#/ directives and exported before the first headline.
> >
> > Comments?
> 
> #+BEGIN_LaTeX and #+END_LaTeX have a more general purpose than just
>  adding "configuration" and you should be able to use them anywhere 
> in the Org source.  
> 
> I think the real question is: what people are doing of #+TEXT?  
> 
> Is it useful as it is now ("this text comes before the first heading,
> overriding the skip option")?  Or should it be redefined so as to mean
> "This piece of text should be inserted in the *header* of the target
> format?"
> 
> Comment?
> 
> -- 
> Bastien
> 
> 
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> address@hidden
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode


------------------------------------------------------------------
Russell Adams                            address@hidden

PGP Key ID:     0x1160DCB3           http://www.adamsinfoserv.com/

Fingerprint:    1723 D8CA 4280 1EC9 557F  66E8 1154 E018 1160 DCB3