[Top][All Lists]

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

Re: Make call-process (and start-process?) filename handlers?

From: Ehud Karni
Subject: Re: Make call-process (and start-process?) filename handlers?
Date: Mon, 13 Jan 2003 13:41:53 +0200

Hash: SHA1

On Mon, 13 Jan 2003 11:21:58 +0100, Andreas Schwab <address@hidden> wrote:
> |> > 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.
> |> 
> |> Stefan and me have precisely the opposite opinion: we find it natural
> |> to execute the program on the remote host, and unnatural to do it
> |> locally.
> It depends, I'd say.  If you just want to do a quick shell command, you
> probably want to execute it locally.  But if you run the shell command on
> the file associated with the buffer it is surely natural to run it on the
> same host where the file resides.  IMHO in most cases you want to run it
> locally, and running remotely should be a special case.

I had this problem with my enhancement to compilations (calling
`compile-internal'). I solved it by letting the user use the prefix
argument (\C-u) to specify a remote compilation.


- -- 
 Ehud Karni           Tel: +972-3-7966-561  /"\
 Mivtach - Simon      Fax: +972-3-7966-667  \ /  ASCII Ribbon Campaign
 Insurance agencies   (USA) voice mail and   X   Against   HTML   Mail
 http://www.mvs.co.il  FAX:  1-815-5509341  / \
 mailto:address@hidden                  Better  Safe  Than  Sorry
Comment: use http://www.keyserver.net/ to get my key (and others)


reply via email to

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