emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Thomas S. Dye <tsd@tsdye.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: emacs-orgmode@gnu.org, Sebastian Boehm <sebastian@sometimesfood.org>
Subject: Re: [PATCH] ox-latex: Add scrartcl LaTeX class
Date: Wed, 23 Sep 2015 08:28:30 -1000	[thread overview]
Message-ID: <m2zj0dng6p.fsf@tsdye.com> (raw)
In-Reply-To: <87vbb1ngqc.fsf@ucl.ac.uk>

Hi Eric,

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

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

I've noticed this, too, but never investigated.

Is there some way to know which variables are "global" and which can be
set "locally"?

Also, (completely naively) is it difficult to make "global" variables
"local", or is it something simple, like making a function interactive?  

All the best,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com

  parent reply	other threads:[~2015-09-23 18:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-21 10:25 [PATCH] ox-latex: Add scrartcl LaTeX class Sebastian Boehm
2015-09-21 19:46 ` Nicolas Goaziou
2015-09-21 21:45   ` Rasmus
2015-09-21 22:37     ` Suvayu Ali
2015-09-22  7:20   ` Eric S Fraga
2015-09-22 11:21     ` Rasmus
2015-09-22 15:33       ` Eric S Fraga
2015-09-22 16:34         ` Rasmus
2015-09-22 14:00     ` Grant Rettke
2015-09-23 16:59   ` Sebastian Boehm
2015-09-23 17:56     ` Thomas S. Dye
2015-09-23 18:16     ` Eric S Fraga
2015-09-23 18:27       ` Ista Zahn
2015-09-24 10:04         ` Eric S Fraga
2015-09-27 13:47           ` Sebastian Boehm
2015-09-23 18:28       ` Thomas S. Dye [this message]
2015-09-23 20:27     ` Rasmus
2015-09-23 20:56       ` Nicolas Goaziou
2015-09-23 21:27         ` Rasmus

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=m2zj0dng6p.fsf@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=sebastian@sometimesfood.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
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).