From: "John Wiegley" <johnw@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: emacs-26 d2d5e54: Mention remote file name completion in Emacs manual
Date: Sun, 04 Feb 2018 00:56:54 -0800 [thread overview]
Message-ID: <m2inbduo89.fsf@newartisans.com> (raw)
In-Reply-To: <87lgg9xhwl.fsf@gmx.de> (Michael Albinus's message of "Sun, 04 Feb 2018 09:45:14 +0100")
>>>>> "MA" == Michael Albinus <michael.albinus@gmx.de> writes:
MA> There is one exception: If you type two slashes at the top of the local
MA> part of a remote file name, it behaves like for local file names. That
MA> means, "/ssh:host:// TAB" completes to "/".
MA> I don't remember why we have done this, but for consistency reasons,
MA> "/ssh:host:// TAB" should complete to "/ssh:host:/", and "/ssh:host:///
MA> TAB" should complete to "/".
MA> Opinions?
Maybe that you'd be changing 30 years of muscle memory on people? I use //
several times a day to "Get back to root", when I don't want to complete
within a sub-path. It also works in places (like ivy) where C-a C-k doesn't
always.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
next prev parent reply other threads:[~2018-02-04 8:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180203203124.9577.74338@vcs0.savannah.gnu.org>
[not found] ` <20180203203125.63A2520690@vcs0.savannah.gnu.org>
2018-02-04 8:45 ` emacs-26 d2d5e54: Mention remote file name completion in Emacs manual Michael Albinus
2018-02-04 8:56 ` John Wiegley [this message]
2018-02-04 9:08 ` Michael Albinus
2018-02-04 15:28 ` Clément Pit-Claudel
2018-02-04 17:18 ` Eli Zaretskii
2018-02-04 18:21 ` Michael Albinus
2018-02-04 20:05 ` John Wiegley
2018-02-04 22:07 ` Michael Albinus
2018-02-05 3:22 ` John Wiegley
2018-02-05 13:08 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2inbduo89.fsf@newartisans.com \
--to=johnw@gnu.org \
--cc=eliz@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 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.