unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Feature request: new function start-remote-process
Date: Wed, 27 Jun 2007 12:37:53 +0200	[thread overview]
Message-ID: <nqy7i53cou.fsf@alcatel-lucent.de> (raw)
In-Reply-To: <jwvfy4eu4xr.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 26 Jun 2007 11:17:03 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> In order not to derogate(?) to the custom of objecting late, I'll add an
> objection right now: the name is wrong because it indicates for what you use
> the feature rather than what it does.  I think that the name should include
> "file" somewhere rather than (or at least additionally to) "remote", since
> the key aspect compared to start-process is that it's a file-name operation.
> So I'd call it "start-file-process".  Other than that, I fully support this
> feature, of course.

"start-remote-process" was proposed by Richard 2 years ago, see
<http://lists.gnu.org/archive/html/emacs-devel/2005-05/msg00769.html>.
He did also propose a new parameter, but I believe the file name
handler check based on default-directory is sufficient.

But I don't believe that the key aspect of "start-remote-process" is a
file-name operation. That is true for process-file only. There one
could have a remote file name specified in INFILE or BUFFER, and
PROGRAM would use a local copy of the file(s) if default-directory is
located on another host. PROGRAM could also run on a remote host if
default-directory is a remote file name.

In start-process as well as in "start-remote-process", you cannot pass
a file name as argument to PROGRAM. Consequently, "start-remote-process"
is not a file-name operation as process-file. Only the possibility to
run PROGRAM on another host is similar to what process-file offers.

Anyway, it is not important to me which name is chosen.

>         Stefan

Best regards, Michael.

  reply	other threads:[~2007-06-27 10:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-17 13:45 Feature request: new function start-remote-process Michael Albinus
2007-06-17 14:40 ` Sean O'Rourke
2007-06-17 16:04   ` Michael Albinus
2007-06-25 18:49 ` Michael Albinus
2007-06-25 19:53   ` Richard Stallman
2007-06-25 20:00     ` David Kastrup
2007-06-25 21:37     ` Michael Albinus
2007-06-26 16:57       ` Richard Stallman
2007-06-26 18:57         ` Michael Albinus
2007-06-26 19:27           ` Michael Albinus
2007-06-26 15:17   ` Stefan Monnier
2007-06-27 10:37     ` Michael Albinus [this message]
2007-06-29 21:12     ` Michael Albinus
2007-06-30  2:40       ` Stefan Monnier
2007-06-30  8:43         ` Michael Albinus
2007-06-26 15:22   ` Stefan Monnier
2007-06-27 10:48     ` Michael Albinus

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=nqy7i53cou.fsf@alcatel-lucent.de \
    --to=michael.albinus@gmx.de \
    --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).