From mboxrd@z Thu Jan 1 00:00:00 1970 From: Klaus-Dieter Bauer Subject: Re: Portable formatting of export? Date: Tue, 22 Oct 2013 17:05:02 +0200 Message-ID: References: <87sivus8jz.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=047d7b624a3c7944a904e955bb86 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46498) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VYdWe-0003Ol-3L for emacs-orgmode@gnu.org; Tue, 22 Oct 2013 11:05:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VYdWY-0003zd-Pk for emacs-orgmode@gnu.org; Tue, 22 Oct 2013 11:05:40 -0400 Received: from mail-ve0-x236.google.com ([2607:f8b0:400c:c01::236]:32856) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VYdWY-0003zR-5G for emacs-orgmode@gnu.org; Tue, 22 Oct 2013 11:05:34 -0400 Received: by mail-ve0-f182.google.com with SMTP id oy12so5138646veb.41 for ; Tue, 22 Oct 2013 08:05:33 -0700 (PDT) In-Reply-To: <87sivus8jz.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Eric Schulte , org-mode mailing list --047d7b624a3c7944a904e955bb86 Content-Type: text/plain; charset=UTF-8 There are several problems with this approach: 1. In order to force default behaviour, I'd have to set ALL customization variables of org explicitly (can be avoided by using an "emacs -q" session for compiling). 2. Even setting just a single setting can be very verbose (e.g. when defining a new document class). 3. The variables are not flagged as safe for use as file-local variables, requiring extra user-interaction whenever the file is visited. Sure, those are all mere convenience issues, but they add up to enough potential inconvenience for cooperative authoring (i.e. the file being edited in different emacs configurations by different people) to make direct latex editing rather attractive. Is that scenario simply outside the scope of org-mode? - Klaus-Dieter Bauer 2013/10/21 Eric Schulte > This can be done with file local variables. See the following page of > the Emacs manual. > > (info "(emacs)Specifying File Variables") > > Klaus-Dieter Bauer writes: > > > Hello! > > > > I have customized org export to both html and latex extensively since I > > disliked many of the defaults (e.g. the use of article vs scrartcl, red > > borders around pdf hyperlinks). > > > > This left me wondering however, if it is possible to create org files > that > > will produce the same output on every machine, regardless of the local > > emacs customizations (of course assuming that no hacks of the export > engine > > are part of the configuration). > > > > In order to make the files more portable I have been trying to make > changes > > affecting export with things like #+LATEX_HEADER: but e.g. changing the > > documentclass to scrartcl seems to be possible only by changing a > > customization variable (org-latex-classes). > > > > Is it possible to make the export engine assume defaults for all > > customization variables for a file (preferably through an in-file > setting) > > and to specify those customization inside the file? > > > > - Klaus > > -- > Eric Schulte > https://cs.unm.edu/~eschulte > PGP: 0x614CA05D > --047d7b624a3c7944a904e955bb86 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
There are several problems with this approach:

1. In order to force default behaviour, I'd have to set ALL cus= tomization variables of org explicitly (can be avoided by using an "em= acs -q" session for compiling).=C2=A0
2. Even setting just a single setting can be very verbose (e.g. when d= efining a new document class).=C2=A0
3. The variables are not fla= gged as safe for use as file-local variables, requiring extra user-interact= ion whenever the file is visited.

Sure, those are all mere convenience issues, but they a= dd up to enough potential inconvenience for cooperative authoring (i.e. the= file being edited in different emacs configurations by different people) t= o make direct latex editing rather attractive.=C2=A0

Is that scenario simply outside the scope of org-mode?<= /div>

- Klaus-Dieter Bauer=C2=A0



2013/10/21= Eric Schulte <schulte.eric@gmail.com>
This can be done with file local variables. = =C2=A0See the following page of
the Emacs manual.

=C2=A0 (info "(emacs)Specifying File Variables")

Klaus-Dieter Bauer <baue= r.klaus.dieter@gmail.com> writes:

> Hello!
>
> I have customized org export to both html and latex extensively since = I
> disliked many of the defaults (e.g. the use of article vs scrartcl, re= d
> borders around pdf hyperlinks).
>
> This left me wondering however, if it is possible to create org files = that
> will produce the same output on every machine, regardless of the local=
> emacs customizations (of course assuming that no hacks of the export e= ngine
> are part of the configuration).
>
> In order to make the files more portable I have been trying to make ch= anges
> affecting export with things like #+LATEX_HEADER: but e.g. changing th= e
> documentclass to scrartcl seems to be possible only by changing a
> customization variable (org-latex-classes).
>
> Is it possible to make the export engine assume defaults for all
> customization variables for a file (preferably through an in-file sett= ing)
> and to specify those customization inside the file?
>
> - Klaus

--
Eric Schulte
https://cs.unm.e= du/~eschulte
PGP: 0x614CA05D

--047d7b624a3c7944a904e955bb86--