From: "Tassilo Horn" <tsdh@gnu.org>
To: "Arash Esbati" <arash@gnu.org>,
"Sebastian Urban" <mrsebastianurban@gmail.com>
Cc: 36357@debbugs.gnu.org
Subject: bug#36357: Wrong Ghostscript program name on MS Win
Date: Tue, 21 Apr 2020 15:19:54 +0200 [thread overview]
Message-ID: <3f0dcce2-8837-4ef9-8981-3aa5864ca15f@beta.fastmail.com> (raw)
In-Reply-To: <86d0817zdd.fsf@gnu.org>
Hi Arash,
looks right to me. Can you commit for yourself or should I do it for you?
Bye,
Tassilo
Am Di, 21. Apr 2020, um 15:16, schrieb Arash Esbati:
> Arash Esbati <arash@gnu.org> writes:
>
> > I don't use doc-view, so I can't really tell, but preview.el (part of
> > AUCTeX) uses "executable-find". Applied to
> > `doc-view-ghostscript-program', it could look like this:
>
> Following up myself, I suggest the patch attached.
>
> @Tassilo: What do you think, does it make sense?
>
> Best, Arash
>
>
> Dateianhänge:
> * 0001-Improve-detection-of-Ghostscript-executable.patch
next prev parent reply other threads:[~2020-04-21 13:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 16:04 bug#36357: Wrong Ghostscript program name on MS Win Sebastian Urban
2019-07-06 8:13 ` Eli Zaretskii
2019-07-06 11:29 ` Tassilo Horn
2019-07-06 11:52 ` Eli Zaretskii
2019-07-06 11:51 ` Eli Zaretskii
2020-03-18 17:26 ` Sebastian Urban
2020-03-18 18:25 ` Eli Zaretskii
2020-03-18 19:23 ` Sebastian Urban
2020-04-13 19:10 ` Sebastian Urban
2020-04-20 20:57 ` Arash Esbati
2020-04-21 13:16 ` Arash Esbati
2020-04-21 13:19 ` Tassilo Horn [this message]
2020-04-21 13:25 ` Arash Esbati
2020-04-21 17:51 ` Sebastian Urban
2020-04-21 18:34 ` Tassilo Horn
2020-04-21 18:48 ` Eli Zaretskii
2020-04-21 20:29 ` Arash Esbati
2020-04-22 9:05 ` Tassilo Horn
2020-04-22 10:07 ` Sebastian Urban
2020-04-22 13:00 ` Tassilo Horn
2020-04-22 13:50 ` Eli Zaretskii
2020-04-22 13:45 ` Eli Zaretskii
2020-04-22 14:14 ` Tassilo Horn
2020-04-22 14:32 ` Eli Zaretskii
2020-04-22 17:29 ` Tassilo Horn
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3f0dcce2-8837-4ef9-8981-3aa5864ca15f@beta.fastmail.com \
--to=tsdh@gnu.org \
--cc=36357@debbugs.gnu.org \
--cc=arash@gnu.org \
--cc=mrsebastianurban@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.