emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Leo Vivier <leo.vivier@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Modifying org-latex-pdf-process doesn't modify the async export behaviour
Date: Sat, 7 Apr 2018 11:16:58 +0200	[thread overview]
Message-ID: <30b544e2-e36b-f917-3e06-1cb2df048a53@gmail.com> (raw)
In-Reply-To: <87woxj5twk.fsf@nicolasgoaziou.fr>

Hello,

Thank you for pointing me in the right direction. I've created another 
init file just for async-export, and not only have I got it to work, but 
it's also quite a lot faster than it used to be.

All that remains now is to find a way to re-write my function. My 
knowledge of elisp if fairly limited, and I don't see how to communicate 
with the background process other than by writing the value of my 
toggle-variable to a file. I guess I could also make a modularise 
async-init.el and control which module is loaded from the main init.el.

At any rate, thank you for your prompt reply.

Best,

On 07/04/18 09:59, Nicolas Goaziou wrote:
> Hello,
> 
> Leo Vivier <leo.vivier@gmail.com> writes:
> 
>> I've encountered an issue trying to write a function to toggle between
>> two org-latex-pdf-process states (short & long). The function works as
>> intended when using synchronous export (the PDF is created with the
>> appropriate number of steps), but it doesn't work with asynchronous
>> export (org-latex-pdf-process isn't grabbed past the first run).
> 
> [...]
> 
>> I've tried appending (org-reload) to my function, but it didn't work.
>> I've also tried modifying org-latex-pdf-process on a fresh emacs
>> session prior to any async export, and I can confirm that it grabs the
>> latest state of org-latex-pdf-process. I'd surmise that async export
>> has a process running in the background, but I don't know how to force
>> it to reload.
> 
> The background process doesn't use whatever configuration is loaded in
> current Emacs. Instead it loads a configuration file. See
> `org-export-async-init-file'.
> 
> You may also use local variables in your document, or switch async
> configuration files.
> 
> Regards,
> 

-- 
Leo Vivier
English Studies & General Linguistics
Master Student, English Department
Rennes 2

next prev parent reply	other threads:[~2018-04-07  9:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-06  9:13 Bug: Modifying org-latex-pdf-process doesn't modify the async export behaviour Leo Vivier
2018-04-07  7:59 ` Nicolas Goaziou
2018-04-07  9:16   ` Leo Vivier [this message]
2018-04-07  9:44     ` Neil Jerram
2018-04-07 10:41     ` 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=30b544e2-e36b-f917-3e06-1cb2df048a53@gmail.com \
    --to=leo.vivier@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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

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