Eli Zaretskii wrote:
In the case of Ghostscript it is actually quite complicated. I have code
for finding Ghostscript in the file w32-regdat.el which is part of
EmacsW32. This uses an external program to read the Registry. The actual
Registry interface is in w32-reg-iface.el (also in EmacsW32).
Are you saying that w32-regdat.el's method of finding Ghostscript is
how other programs, like GSView, find it? This is so ridiculously
complicated that it's simpler to tell the users "add the GS directory
to your PATH".
Yes, this is how GSView does it. I believe there might be a point in
doing it the same way as GSView does it.
Note that the node "MS-DOS Printing" (which deals with Windows as well
as DOS problems) already advises to use a full absolute file name of
the Ghostscript executable in setting up ps-lpr-command. Is this the
only place where a user would need to know the Ghostscript
installation directory?
I believe so, is not printing.el using this too? The only thing I do is
setting up this automatically for the user (since Ghostscript/GSview are
not in the path).
Finding GSview is in contrast very simple since it is in App Paths.
But we shouldn't need to launch GSview, should we?
I think I added this because printing.el uses it.
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
