From: Richard Stallman <rms@gnu.org>
Cc: eliz@gnu.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: executable-find in files.el
Date: Wed, 18 May 2005 09:08:00 -0400 [thread overview]
Message-ID: <E1DYOHI-0002Lp-OQ@fencepost.gnu.org> (raw)
In-Reply-To: <87k6lzots5.fsf@gmx.de> (message from Michael Albinus on Mon, 16 May 2005 21:27:54 +0200)
But during migrating existing packages, the drawback has
been obvious: Everywhere there is the need of checking a command for
being remote or not, and then to call `process-file' or
`call-process'.
I can't see why you did that. If in a certain call you want
the file name handler to be used, you can unconditionally call
process-file. Why didn't you do that?
If `call-process' would be able to handle remote
commands, most of the cases nothing would be needed to be changed -
the existing code would simply work. And the same for `start-process'.
This would be an incompatible change, and I am not convinced it is
correct or meaningful. The definition of call-process is that it runs
the command you specified. I does not seem right for the mere choice
of default-directory should have such a major effect on call-process.
Conceptually, process-file is different.
And the same for `start-process'.
Likewise the mere default-directory should not have such a drastic
effect on start-process. If we have a facility to start a process
on a possibly-remote machine, we should specify it differently.
Perhaps with a new function start-remote-process that has a new arg
that says which machine. When that arg is nil, it would be equivalent
to start-process.
prev parent reply other threads:[~2005-05-18 13:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1DVuFh-0001h1-GE@monty-python.gnu.org>
2005-05-11 18:29 ` executable-find in files.el Eli Zaretskii
2005-05-11 19:07 ` Stefan Monnier
2005-05-11 22:56 ` Eli Zaretskii
2005-05-11 23:16 ` Stefan Monnier
2005-05-11 23:50 ` David Kastrup
2005-05-12 1:31 ` Stefan Monnier
2005-05-12 6:34 ` Eli Zaretskii
2005-05-12 12:42 ` Stefan Monnier
2005-05-12 13:14 ` Eli Zaretskii
2005-05-14 14:58 ` Michael Albinus
2005-05-15 0:21 ` Richard Stallman
2005-05-16 19:27 ` Michael Albinus
2005-05-16 22:38 ` Stefan Monnier
2005-05-17 22:03 ` Kim F. Storm
2005-05-17 22:23 ` Stefan Monnier
2005-05-18 13:08 ` Richard Stallman
2005-05-17 4:36 ` Richard Stallman
2005-05-17 16:32 ` Michael Albinus
2005-05-18 5:19 ` Richard Stallman
2005-05-18 13:08 ` Richard Stallman [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1DYOHI-0002Lp-OQ@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.