On Wed, Sep 23, 2015 at 2:16 PM, Eric S Fraga <e.fr...@ucl.ac.uk> wrote: > On Wednesday, 23 Sep 2015 at 18:59, Sebastian Boehm wrote: >> Hi Nicolas, >> >> On 21 September 2015 at 21:46, Nicolas Goaziou <m...@nicolasgoaziou.fr> >> wrote: >>> But can't users needing a non-default class customize their >>> own `org-latex-classes? Or is there an entitling reason to offer it out >>> of the box? >> >> you are of course right; users can always customise their own setup. >> However, when sharing Org files with other people this kind of tight >> coupling between the Org file and the user's Emacs configuration can >> become quite problematic. > > Yes, this is a real problem. > > One solution, but not an ideal one, is to use file local variables to > define org-latex-classes (and any other variables) as appropriate for > the document. It's not ideal because unfortunately most of org's > variables (as well as many of emacs's own) are "global" and hence affect > the functionality of org visiting other buffers. I find myself having > separate emacs instances for some org files for this reason.
Doesn't "setq-local" solve this problem? > > I had thought that maybe using #+bind: would solve this problem but the > export engine looks for the LaTeX class before binding takes effect. > > -- > : Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.2, Org release_8.3.1-270-g256fef >
