[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Emacs-diffs] master 37b88d7: Fix bug#23006

From: Stefan Monnier
Subject: Re: [Emacs-diffs] master 37b88d7: Fix bug#23006
Date: Fri, 10 Mar 2017 05:57:01 -0500
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux)

> I hate this ambiguity since ever (I've entered Tramp maintenace in
> 2002).  But we are much too late to change the syntax.

Of course not.  It can be changed very easily, and very few users if any
will suffer from it.  In all likelihood the only cases where this
occurs are interactive situations, and we've generally considered it OK
to break backward compatibility with "old humans" (as opposed to "old
code", where we usually try to preserve this compatibility) except for
specific cases where we think that it will inconvenience muscle memory of
too many users.

Let's get rid of this ambiguity once and for all, so we can move on,
instead of adding hacks to try and keep it alive even longer.

>> The binding you added gets rid of this distinction, and indeed, now if
>> I do `C-x C-f /ssh:foo:bar TAB' I don't get any completion any more.
> A single "/" helps. Try `C-x C-f /ssh:foo:./bar TAB' for example.

So I see another problem:

   emacs -Q
   M-x icomplete-mode RET
   C-x C-f /ssh:foo:/

and now suddenly it's signaling errors because it tries to connect to
`foo` even though I haven't requested any completion yet.
I think it should honor `non-essential' in that case and not try to open
up a new connection until I hit TAB or some similar explicit request.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]