emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Julien Cubizolles <j.cubizolles@free.fr>
To: emacs-orgmode@gnu.org
Subject: Re: org-latex-image-default-width ignored
Date: Mon, 26 Mar 2018 10:39:58 +0200	[thread overview]
Message-ID: <87h8p3kz6p.fsf@free.fr> (raw)
In-Reply-To: 87bmfcweqs.fsf@gmail.com

Eric S Fraga <esflists@gmail.com> writes:

> On Sunday, 25 Mar 2018 at 09:52, Julien Cubizolles wrote:
>> Found the cause of the problem, my default configuration exports in
>> async mode, so this variable should be set in
>> org-export-async-init.el.
>>
>> Is there a way to have a variable set during export to avoid setting it
>> for all exports?
>
> I've never used the async export so I am not sure but maybe check out
> the #+bind: directive?

I tried

--8<---------------cut here---------------start------------->8---
#+BIND: org-latex-image-default-width ".3\\linewidth"
--8<---------------cut here---------------end--------------->8---

with no success in async mode, but it works in synchronous mode. I guess
I'll avoid async mode for now on, or use a set of different
org-export-async-init.el files for different files.

Nevertheless I think it would make sense to have a way to set some
variables during async export. According to the Org Manual:

--8<---------------cut here---------------start------------->8---
Emacs variables can become buffer-local during export by using the BIND
keyword.  Its syntax is ‘#+BIND: variable value’.  This is particularly
useful for in-buffer settings that cannot be changed using keywords.
--8<---------------cut here---------------end--------------->8---

But the options set using #+ keywords are used during async export while
those set using #+BIND are ignored. A "+BIND-ASYNC would come in handy.

Julien.

      reply	other threads:[~2018-03-26  8:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-24 15:20 org-latex-image-default-width ignored Julien Cubizolles
2018-03-24 17:57 ` Eric S Fraga
2018-03-25  7:52   ` Julien Cubizolles
2018-03-25 11:56     ` Eric S Fraga
2018-03-26  8:39       ` Julien Cubizolles [this message]

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=87h8p3kz6p.fsf@free.fr \
    --to=j.cubizolles@free.fr \
    --cc=emacs-orgmode@gnu.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).