Ista Zahn <[email protected]> writes:
> I've been having trouble generating previews on windows, and finally
> tracked it down to preview.el not finding gswin64c.exe (despite this
> being in my PATH preview-gs-command was nil) installed from
> http://www.ghostscript.com/download/gsdnld.html. I had to install the
> 32 bit version (also from
> http://www.ghostscript.com/download/gsdnld.htm) and add that to by
> PATH, after which preview-gs-command was correctly set and previews
> worked. Is this known/expected that 64 bit ghostscript will not work?
dak@lola:/usr/local/tmp/auctex$ git grep -i gswin..c
ChangeLog-preview: `system-type', using "GSWIN32C.EXE" on `windows-nt'.
ChangeLog-preview: gswin32c.exe as a problem source.
ChangeLog-preview: * doc/wininstall.texi: Add note about `gswin32c.exe'.
configure.ac: AC_CHECK_PROGS(GS, gs GSWIN32C.EXE, NONE)
configure.ac: EMACS_LISP([[lispGS]],[[(if (member dir (list \"NONE\" (if (eq
system-type 'windows-nt) \"GSWIN32C.EXE\" \"gs\"))) \"\" \`(defvar
preview-gs-command ,dir))]],-no-site-file,[[dir]],[["${GS}"]])
doc/wininstall.texi:gswin32c -h
doc/wininstall.texi:GS="@var{drive:/path/to/gswin32c.exe}" ./configure @dots{}
doc/wininstall.texi:should work for this purpose. @file{gswin32c.exe} is the
usual name for
preview.el.in: (executable-find "GSWIN32C.EXE")
dak@lola:/usr/local/tmp/auctex$
So in a way yes. What a stupid naming scheme. Maybe one should look
for gswin32c before gswin64c in case both are installed in a 32 bit
system. But I don't have an actual clue about Windows systems.
--
David Kastrup
_______________________________________________
auctex mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/auctex
