emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: printing.el v6.6.3


From: Vinicius Jose Latorre
Subject: Re: printing.el v6.6.3
Date: Mon, 10 Dec 2001 13:31:30 -0200

>     (defun pr-command (command)
>       "Return a full path specification for COMMAND.
> 
> In GNU, we have a convention that we use the term "path"
> only for lists of directories to search.  I think what you
> mean here is an absolute file name.  So certain names
> should be changed.

I've just changed to:

   "Return absolute file name specification for COMMAND.


> pr-dosify-path actually operates on file names.  But I think the job
> it does is no longer considered desirable; it should probably be
> eliminated, not renamed.  The same for pr-unixify-path.  Eli,
> what do you think?

Unfortunately, there are problems with file name specification when running
Emacs on Windows, specially when a file name is used as an argument for a
command.  Commands like print.exe, gsview.exe, etc. need file name using `\' as
a directory separator.


> However, I have to question the usefulness of the whole pr-path-alist
> feature.  Many Emacs packages find commands to run.  Normally they
> find these commands either through $PATH or through variables that
> specify the command name (which can be a file name) to do a certain
> job.
> 
> It seems to me that there is no particular reason to add this new
> mechanism for printing commands alone.  It makes Emacs as a whole
> incoherent, and it is unnecessary complexity.  We should just tell
> people, "either put those directories in $PATH or set the following
> six variables".

Some users complained about maintaining printing initializations on several
plataforms, that is, a user running Emacs on Windows and GNU/Linux.  The idea
was to minimize variable settings, specially settings of commands.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]