emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: Spike Spiegel <fsmlab@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: questions about exporting to latex using beamer documentclass
Date: Sun, 05 Jul 2009 12:40:38 -0400	[thread overview]
Message-ID: <20141.1246812038@gamaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Spike Spiegel <fsmlab@gmail.com> of "Sun, 05 Jul 2009 12:52:32 BST." <ab777dfe0907050452h5e8c6e3ep539843847768eaca@mail.gmail.com>

Spike Spiegel <fsmlab@gmail.com> wrote:

> ... 
> Also, given a variable like org-export-latex-image-default-option, is
> there any way to override it per file or per document class?
> ... 

Well, yes and no (mostly no - but see below):

o You can of course customize this variable, but that's a global setting.

o You can use the ":latex-image-options" property to set the above variable,
  but that is used in org-publish-project-alist, not for exporting. From org-exp.el:

| (defconst org-export-plist-vars
|   '((:link-up		      nil	  org-export-html-link-up)
|     ...
|     (:latex-image-options     nil	  org-export-latex-image-default-option))
|   "List of properties that represent export/publishing variables.
| Each element is a list of 3 items:
| 1. The property that is used internally, and also for org-publish-project-alist
| 2. The string that can be used in the OPTION lines to set this option,
|    or nil if this option cannot be changed in this way
| 3. The customization variable that sets the default for this option."
| )

o You can modify the setting of the org-export-plist-vars (either by modifying your copy
  of org-exp.el or by some other method) to change the line

     (:latex-image-options     nil	  org-export-latex-image-default-option))


     (:latex-image-options     "latex-image-options"	  org-export-latex-image-default-option))

  and then use

     #+OPTIONS: latex-image-options:width=1cm

  in your org file.

  [BTW, if you are using git, small local variations from the canonical org-mode can be easily
   accommodated, by using a local branch and git rebase.]

o You can try to convince Carsten that this should be part of canonical org-mode.


  parent reply	other threads:[~2009-07-05 16:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fsmlab@gmail.com>
2009-07-04 23:31 ` Spike Spiegel
2009-07-05  1:34   ` Nick Dokos
2009-07-05  3:40   ` Nick Dokos
2009-07-05 11:52     ` Spike Spiegel
2009-07-05 15:24       ` Nick Dokos
2009-07-05 15:38       ` Nick Dokos
2009-07-05 16:40       ` Nick Dokos [this message]
2009-07-06 16:24         ` Carsten Dominik
2009-07-05 21:25   ` Russell Adams

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:

  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=20141.1246812038@gamaville.dokosmarshall.org \
    --to=nicholas.dokos@hp.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=fsmlab@gmail.com \
    --subject='Re: questions about exporting to latex using beamer documentclass' \


* 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 inbox:


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