From: Michael Albinus <michael.albinus@gmx.de>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 10319@debbugs.gnu.org
Subject: bug#10319: 24.0.92; doc string of `file-remote-p'
Date: Tue, 20 Dec 2011 18:02:57 +0100 [thread overview]
Message-ID: <87ehvzch1a.fsf@gmx.de> (raw)
In-Reply-To: <7ED9EAB31656456981FDB12C5ABD0C7B@us.oracle.com> (Drew Adams's message of "Tue, 20 Dec 2011 07:53:24 -0800")
"Drew Adams" <drew.adams@oracle.com> writes:
> Are you saying that nil is always returned for a relative file name? If so,
> let's just say that: "Return nil if FILE is a relative file name". (No need to
> say that you must or should use an absolute name.)
Thinking about (and testing a little bit) it seems like this: for
relative file names it always returns nil, indeed. This is because it
does not apply `expand-file-name'. Your proposed sentence looks OK.
>> When IDENTIFICATION is nil, the returned string is everything
>> until the last ":" (with expanded default method, default user,
>> default host).
>>
>> (file-remote-p "/sudo::/") => "/sudo:root@localhost:"
>> (file-remote-p "/localhost:/") => "/scpc:localhost:"
>
> Fine. Let's say that (it's not obvious, IMHO).
>
> When IDENTIFICATION is nil, the returned string is a complete
> remote identifier: with components method, user, and host.
> The components are those present in FILE, with defaults filled
> in for any that are missing.
OK.
>> What I have tried to explain is a common technique for creation of new
>> remote filenames, derived from an existing one. Let's say you have a
>> variable `file' containing the remote filename "/sudo::/path/to/file",
>> and you want to create a new remote filename for the file
>> "/bin/sh". You apply then (concat (file-remote-p file) "/bin/sh")
>
> That's a useful tip about another way to _use_ the function, and also not so
> obvious. Let's say that too.
>
> Tip: You can use this expansion of remote identifier components
> to derive a new remote name from an existing one. For example,
> if FILE is "/sudo::/path/to/file" then
> (concat (file-remote-p FILE) "/bin/sh") returns a remote
> name for file "/bin/sh" that has the same remote identifier as
> FILE but expanded; a name such as "/sudo:myhost.org:/bin/sh".
OK as well. Minor change: the result for the sudo case ought to be
"/sudo:root@myhost:/bin/sh". "root" is the default user name for "sudo",
and "myhost" instead of "myhost.org" because the default host name in
this case is the value of `system-name'.
> HTH.
Thanks, and best regards, Michael.
next prev parent reply other threads:[~2011-12-20 17:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-18 2:17 bug#10319: 24.0.92; doc string of `file-remote-p' Drew Adams
2011-12-18 8:33 ` Michael Albinus
2011-12-18 15:02 ` Drew Adams
2011-12-19 8:40 ` Michael Albinus
2011-12-19 16:10 ` Drew Adams
2011-12-19 18:26 ` Michael Albinus
2011-12-19 19:44 ` Drew Adams
2011-12-19 21:18 ` Michael Albinus
2011-12-19 21:29 ` Drew Adams
2011-12-20 9:15 ` Michael Albinus
2011-12-20 15:53 ` Drew Adams
2011-12-20 17:02 ` Michael Albinus [this message]
2011-12-20 17:08 ` Drew Adams
2011-12-20 17:14 ` Michael Albinus
2011-12-20 17:33 ` Drew Adams
2011-12-21 18:34 ` 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=87ehvzch1a.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=10319@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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).