From: David Kastrup <dak@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: Uncomprehensible DOC string
Date: Fri, 09 May 2008 11:39:41 +0200 [thread overview]
Message-ID: <86lk2jn7du.fsf@lola.quinscape.zz> (raw)
In-Reply-To: <nqve1nn7kp.fsf@alcatel-lucent.de> (Michael Albinus's message of "Fri, 09 May 2008 11:35:34 +0200")
Michael Albinus <michael.albinus@gmx.de> writes:
> David Kastrup <dak@gnu.org> writes:
>
>> No, but saying a file name handler will be called based on
>> default-directory without telling what the file name handler is actually
>> supposed to be processing is not much use I think. The command? The
>> command line arguments? The executable?
>
> _The_ file name handler, which belongs to `default-directory', will be
> applied.
To what will it be applied?
> Currently, there ought to be only one implementation of such a file
> name handler, `tramp-handle-start-file-process'. _This_ file name
> handler runs the command on the corresponding remote host.
So what the file name handler will be employed for is executing the
program on potentially remote host. This information is _absent_ from
the DOC string, and it shouldn't. In contrast, what a file name handler
_is_, is best left to the info documentation.
--
David Kastrup
next prev parent reply other threads:[~2008-05-09 9:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 11:32 Uncomprehensible DOC string David Kastrup
2008-05-09 5:20 ` Michael Albinus
2008-05-09 6:55 ` David Kastrup
2008-05-09 7:53 ` Michael Albinus
2008-05-09 8:30 ` David Kastrup
2008-05-09 9:35 ` Michael Albinus
2008-05-09 9:39 ` David Kastrup [this message]
2008-05-09 13:54 ` Michael Albinus
2008-05-09 14:21 ` David Kastrup
2008-05-09 15:30 ` 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=86lk2jn7du.fsf@lola.quinscape.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.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).