Re: [Bug-AUCTeX] preview-latex

[David Kastrup]

"Marcel Fischer" <address@hidden> writes:

[...]

> DviPS sentinel: Searching for program: no such file or directory, GSWIN32C.EXE

[...]

> Output from running `GSWIN32C.EXE -h':

[blank]


Did you actually read your report before posting it?  It is obvious
that Ghostscript is not installed, or not in your PATH variable.

INSTALL.windows has this to say:

In a nutshell:

[...]

     If the configuration script failed to find all required programs,
     make sure that these programs are in your system path and add
     directories containing the programs to the `PATH' environment
     variable if necessary.  Here is how to do that in W2000/XP:

       1. On the desktop, right click "My Computer" and select
          properties.

       2. Click on "Advanced" in the "System Properties" window.

       3. Select "Environment Variables".

       4. Select "path" in "System Variables" and click "edit".  Move
          to the front in the line (this might require scrolling) and
          add the missing path including drive letter, ended with a
          semicolon.

[...]

Prerequisites:

[...]

  5. A working copy of Ghostscript (http://www.cs.wisc.edu/~ghost) is
     required for preview-latex operation.  Examining the output from
          gswin32c -h
     on a Windows command line should tell you whether your Ghostscript
     supports the `png16m' device needed for PNG support.  MiKTeX
     apparently comes with its own Ghostscript called `mgs.exe'.

[...]


     Some executables might not be found in your path.  That is not a
     good idea, but you can get around by specifying environment
     variables to `configure':
          GS="DRIVE:/PATH/TO/GSWIN32C.EXE" ./configure ...
     should work for this purpose.  `gswin32c.exe' is the usual name for
     the required _command line_ executable under Windows; in contrast,
     `gswin32.exe' is likely to fail.

     As an alternative to specifying variables for the `configure' call
     you can add directories containing the required executables to the
     `PATH' variable of your Windows system.  This is especially a good
     idea if Emacs has trouble finding the respective programs later
     during normal operation.

[...]


-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum