From: Michael Albinus <michael.albinus@gmx.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Saving a remote buffer into a local file
Date: Wed, 25 Jan 2017 10:51:01 +0100 [thread overview]
Message-ID: <87fuk731tm.fsf@gmx.de> (raw)
In-Reply-To: <jwvvat4zbka.fsf-monnier+gmane.emacs.help@gnu.org> (Stefan Monnier's message of "Tue, 24 Jan 2017 11:10:06 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> Suppose I visit some remote file:
>> C-x C-f /ssh:user1@host1:/path1/file1
>> Now, I want to save the resulting buffer into a local file. Doing:
>> C-x C-w ~/file2
>> does not work, since in will create a file in the remote host (host1).
>
> It works for me if I add a "C-a C-k":
>
> C-x C-w C-a C-k ~/file2
>
> Yet, if I do like you suggest, I see a bug: while typing "~/file2" the
> leading "/ssh:user1@host1:/path1/" text is greyed out, giving the
> incorrect impression that it won't be used.
No. Only "/path1/" is greyed out, telling you that *this* part won't be
used.
Remote file names have a special meaning of double slash and slash tilde
in file name completion. It removes the leading part of the remote file
name's local part. You need another slash for removing the whole file
name in the minibuffer. Therefore, doing
C-x C-w /~/file2
would suffice. You will see also the grey part of the minibuffer being
changed to the whole line. Personally, when I want to save a remote file
locally, I have the attitude typing three slashes first. Meanwhile, I do
this even w/o thinking about :-)
See (info "(tramp) File name completion") for discussion.
> Stefan
Best regards, Michael.
prev parent reply other threads:[~2017-01-25 9:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 9:07 Saving a remote buffer into a local file Dani Moncayo
2017-01-24 9:37 ` Dani Moncayo
2017-01-24 16:00 ` Eli Zaretskii
2017-01-24 16:10 ` Stefan Monnier
2017-01-25 8:42 ` Dani Moncayo
2017-01-25 9:51 ` Michael Albinus [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fuk731tm.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=help-gnu-emacs@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.