From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-26 d2d5e54: Mention remote file name completion in Emacs manual
Date: Sun, 04 Feb 2018 23:07:01 +0100 [thread overview]
Message-ID: <878tc8jtoa.fsf@gmx.de> (raw)
In-Reply-To: <m2a7womsfd.fsf@newartisans.com> (John Wiegley's message of "Sun, 04 Feb 2018 12:05:42 -0800")
John Wiegley <johnw@gnu.org> writes:
Hi John,
> Clément has made me think I'm objecting too broadly. Indeed, these all do what
> I expected in ivy:
>
> /ssh:hermes:/<TAB> completes in / on remote
> /ssh:hermes://<TAB> completes in / on remote
> /ssh:hermes:///<TAB> completes in / on local
>
> Are you saying this is inconsistent for plain Emacs?
Yes. Vanilla Emacs ("emacs -Q") behaves like this:
/ssh:ford:/<TAB> completes in / on remote
/ssh:ford://<TAB> completes in / on local
/ssh:ford:///<TAB> completes in / on remote
The second one is the inconsistency I wrote about (it shall complete in
/ on remote). The third one I didn't recognize until now, it shall
complete in / on local. A bug.
My proposal is the behavior you've shown with ivy, also for vanilla
Emacs.
> John
Best regards, Michael.
next prev parent reply other threads:[~2018-02-04 22:07 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
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 [this message]
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=878tc8jtoa.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@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.
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.