unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
Cc: eliz@gnu.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: executable-find in files.el
Date: Tue, 17 May 2005 18:32:47 +0200	[thread overview]
Message-ID: <umzqtn780.fsf@gmx.de> (raw)
In-Reply-To: <E1DXtpC-0003Nw-4y@fencepost.gnu.org> (Richard Stallman's message of "Tue, 17 May 2005 00:36:58 -0400")

Richard Stallman <rms@gnu.org> writes:

>     Sorry for being too short. I wanted to say that there should be a
>     general concept for running commands on remote hosts.
>
> I would not say that it is a priority for Emacs to have such a thing.
> I think it would be a difficult thing to do.  However, if you design
> one and the design is good, I would be glad to accept it.
>
> Not now, however.  It should wait for after the release.

OK, I'll come back to this later on.

>     Everywhere there is the need of checking a command for
>     being remote or not, and then to call `process-file' or
>     `call-process'.
>
> I don't understand "checking a command for being remote or not".
> I have no idea what this is talking about.

"checking whether a command will be executed on a local or a remote
host". Stefan pointed already to this inaccuracy of mine.

One could argue that just calling `process-file' should be
sufficient. But it isn't for packages which still want to support
Emacs 21. Supporting `call-process´ for commands on remote hosts would
result in no change for such packages in the best case. 

>     If `call-process' would be able to handle remote
>     commands,
>
> I cannot envision any way in which that could make sense.  I have no
> idea what it would mean for `call-process' to "handle" remote
> commands.

"handle commands to be executed on a remote host".

Best regards, Michael.

  reply	other threads:[~2005-05-17 16:32 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 [this message]
2005-05-18  5:19               ` Richard Stallman
2005-05-18 13:08           ` 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=umzqtn780.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --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 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).