From: Richard Stallman <rms@gnu.org>
Cc: kai.grossjohann@uni-duisburg.de
Subject: Re: Make call-process (and start-process?) filename handlers?
Date: Sun, 12 Jan 2003 06:55:50 -0500 [thread overview]
Message-ID: <E18XgiU-0004LZ-00@fencepost.gnu.org> (raw)
In-Reply-To: <200301102352.h0ANqoK01404@rum.cs.yale.edu> (monnier+gnu/emacs@rum.cs.yale.edu)
The `shell-command' precedent as well as the `dired-call-process' precedent
show that there is something to say for `call-process' (and by extension
`start-process') to call a file-name-handler depending on default-directory.
I'm not convinced.
dired-call-process is used for a few specific programs, to operate on
files in the default directory and its subdirectories. In those limited
cases, it should do the right thing.
I'm concerned about shell-command, because it looks like this will
make all shell commands execute remotely when you are visiting a
remote file. That is not natural, and not necessarily correct; it
could cause a painful surprise. It might be ok as a special exception
feature, if it were documented as one. Currently it isn't.
If we did something like this for call-process, I expect it would
break programs that run call-process for specific commands that do not
use the default-directory. They expect the command to do the same
thing regardless of whether default-directory is remote.
next prev parent reply other threads:[~2003-01-12 11:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-28 22:31 Make call-process (and start-process?) filename handlers? Kai Großjohann
2002-12-31 5:47 ` Richard Stallman
2002-12-31 18:54 ` Kevin Rodgers
2003-01-02 18:38 ` Richard Stallman
2003-01-10 23:52 ` Stefan Monnier
2003-01-11 21:33 ` Kai Großjohann
2003-01-13 10:42 ` Richard Stallman
2003-01-12 11:55 ` Richard Stallman [this message]
2003-01-12 14:54 ` Kai Großjohann
2003-01-13 10:21 ` Andreas Schwab
2003-01-13 11:41 ` Ehud Karni
2003-01-14 18:54 ` Richard Stallman
2003-01-14 22:42 ` Luc Teirlinck
2003-01-15 23:28 ` Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E18XgiU-0004LZ-00@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=kai.grossjohann@uni-duisburg.de \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).