From: Tassilo Horn <tsdh@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>,
Sebastian Urban <mrsebastianurban@gmail.com>
Cc: 36357@debbugs.gnu.org
Subject: bug#36357: Wrong Ghostscript program name on MS Win
Date: Sat, 06 Jul 2019 13:29:57 +0200 [thread overview]
Message-ID: <16bc70c3f08.27dc.69bc538c4644581689883e654f15bce0@gnu.org> (raw)
In-Reply-To: <831rz3a8ci.fsf@gnu.org>
No objections from my side.
Bye,
Tassilo
On July 6, 2019 10:13:59 AM Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Sebastian Urban <mrsebastianurban@gmail.com>
>> Date: Mon, 24 Jun 2019 18:04:41 +0200
>>
>> Variable 'doc-view-ghostscript-program' has value - 'gs' - which is OK
>> for Unix and VMS, but NOT OK for MS Windows. It should be 'gswin32c'.
>> For details look at the table in "How to Use Ghostscript", chapter
>> "2.1 Help at the command line: gs -h".
>>
>> Perhaps it should be done as list of choice, like in case of
>> 'tex-dvi-view-command'?
>>
>> Or as S. Monnier wrote: "(...) the default could simply
>> (executable-find "gs") and (executable-find "gswin32c") and use
>> whichever was found (...)".
>>
>> Also the same table says 'gsos2' for OS/2 systems.
>
> Tassilo, any objections to such a change? It sounds TRT to me, but I
> don't use these features, and don't have Ghostscript installed.
>
> Thanks.
>
next prev parent reply other threads:[~2019-07-06 11:29 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 [this message]
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
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16bc70c3f08.27dc.69bc538c4644581689883e654f15bce0@gnu.org \
--to=tsdh@gnu.org \
--cc=36357@debbugs.gnu.org \
--cc=eliz@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.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).