Nick Dokos <> writes:

> Nicolas Goaziou <> writes:

>> Anyway, in a nutshell, your proposal is to:
>>   - add a custom variable, e.g., `org-latex-dvi-process-options' (which
>>     library should it belong to?)
> Unless it would make sense to toss the whole dvipng thing overboard and
> just keep imagemagick.

I'm not sure there is a really good reason to drop it. Is it inferior in
some way?

Also, imagemagick is not optimal either. Since it uses
`org-latex-pdf-process', "pdflatex" is called three times by default,
which is unnecessary for a short snippet.

So, both dvipng and imagemagick should have a variable to set the
program to call, along with its arguments.

>>   - modify `org-latex-listings' docstring (in particular, add third
>>     elements and new custom variable)
> I'm not sure any more that it can all be explained clearly in the
> docstring (at least I've been trying different mental gyrations and I
> have not come up with anything satisfactory). So maybe the thing to do
> is add a page to worg and a pointer to it in the docstring. If that's
> acceptable, I volunteer to write the worg page (at least the initial
> version).

A worg page can't hurt, but a URL in the docstring is not very handy
either. It also defeats the "self-documenting" part of Emacs.

> As a separate issue, I proposed some debugging aids:
>>   - add a custom variable, e.g., `org-latex-dvi-process-debug', which,
>>     when non-nil asks to leave produced "tex" file.
> ... and a call-process-log function that logs the command in *Messages*
> before executing it with call-process (or something more or less
> equivalent). It would be used wherever call-process is used now.
> I would actually propose that the debug variable inhibit the deletion
> of intermediate files everywhere, not just in latex preview.

Some parts of Org already have their own debug variable (see
`org-export-async-debug'). A meta debug variable would not be optimal,
would it?


Nicolas Goaziou

Reply via email to