From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: Saving a remote buffer into a local file
Date: Tue, 24 Jan 2017 11:10:06 -0500 [thread overview]
Message-ID: <jwvvat4zbka.fsf-monnier+gmane.emacs.help@gnu.org> (raw)
In-Reply-To: CAH8Pv0jx649eL5t8P-hv_EoebpKUynqGOaiMp6i+jdZtUvNWCg@mail.gmail.com
> 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.
Stefan
next prev parent reply other threads:[~2017-01-24 16:10 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 [this message]
2017-01-25 8:42 ` Dani Moncayo
2017-01-25 9:51 ` 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=jwvvat4zbka.fsf-monnier+gmane.emacs.help@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=help-gnu-emacs@gnu.org \
/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.
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).