From: Scott Otterson <scotto@sharpleaf.org>
To: Scott Otterson <scotto@sharpleaf.org>,
"Emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Bug: Windows-unfriendly filename in org-preview-latex-process-alist customization
Date: Sun, 27 Nov 2016 22:14:16 +0100 [thread overview]
Message-ID: <CAPY3P0Qnk0D7eZpoZNu_e78ExuJA03zer54FSWFxXeBxoGwjmQ@mail.gmail.com> (raw)
In-Reply-To: <87vav9goqv.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 997 bytes --]
Happy to try it out. Should I expect the change on elpa/org sometime soon?
Scott
On Sun, Nov 27, 2016 at 12:12 PM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:
> Hello,
>
> Scott Otterson <scotto@sharpleaf.org> writes:
>
> > Thanks Fabrice. After more experimentation, I found that image-converter
> > field of the customization alist should be:
> >
> > ("dvipng -fg %F -bg %B -D %D -T tight -o \"%o%b\.png\" %f")
> >
> > If this also works for *nix, then I hope that the org-mode maintainers
> will
> > make this string the new default. If it doesn't work on linux, then I
> hope
> > that it's possible to come up with a string that works in both OS
> families
> > (and that could be the new default). I'll be back on Linux in a few
> > months, and would love to keep a simple, cross-platform .emacs file.
>
> I introduced %O, which is the absolute output file name, as
> a replacement for %o%b.extension.
>
> Could you confirm the bug is fixed?
>
> Regards,
>
> --
> Nicolas Goaziou
>
[-- Attachment #2: Type: text/html, Size: 1581 bytes --]
next prev parent reply other threads:[~2016-11-27 21:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-26 15:41 Bug: Windows-unfriendly filename in org-preview-latex-process-alist customization Scott Otterson
2016-11-26 16:35 ` Fabrice Popineau
2016-11-26 23:15 ` Scott Otterson
2016-11-27 11:12 ` Nicolas Goaziou
2016-11-27 21:14 ` Scott Otterson [this message]
2016-11-27 22:12 ` Nicolas Goaziou
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=CAPY3P0Qnk0D7eZpoZNu_e78ExuJA03zer54FSWFxXeBxoGwjmQ@mail.gmail.com \
--to=scotto@sharpleaf.org \
--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).