unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ehud Karni" <ehud@unix.mvs.co.il>
Cc: kai.grossjohann@uni-duisburg.de
Subject: Re: Make call-process (and start-process?) filename handlers?
Date: Mon, 13 Jan 2003 13:41:53 +0200	[thread overview]
Message-ID: <200301131141.h0DBfrPd021564@beta.mvs.co.il> (raw)
In-Reply-To: <jewul9mjsp.fsf@sykes.suse.de> (message from Andreas Schwab on Mon, 13 Jan 2003 11:21:58 +0100)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 13 Jan 2003 11:21:58 +0100, Andreas Schwab <schwab@suse.de> 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.


- -- 
 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:ehud@unix.mvs.co.il                  Better  Safe  Than  Sorry
-----BEGIN PGP SIGNATURE-----
Comment: use http://www.keyserver.net/ to get my key (and others)

iD8DBQE+IqYBLFvTvpjqOY0RAvqRAJ9kBEfpdRwbtpWtRzlP7VldCGy4NwCeI9/u
hHoquRhjVQZL25SBAO5Y+zE=
=Hn61
-----END PGP SIGNATURE-----

  reply	other threads:[~2003-01-13 11:41 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
2003-01-12 14:54       ` Kai Großjohann
2003-01-13 10:21         ` Andreas Schwab
2003-01-13 11:41           ` Ehud Karni [this message]
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=200301131141.h0DBfrPd021564@beta.mvs.co.il \
    --to=ehud@unix.mvs.co.il \
    --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).