From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 7583@debbugs.gnu.org
Subject: bug#7583: 23.2; ido loads tramp too eagerly
Date: Tue, 18 Oct 2011 07:39:25 +0200 [thread overview]
Message-ID: <87boteq2nm.fsf@gmail.com> (raw)
In-Reply-To: <jwvd3dvo1py.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 17 Oct 2011 15:36:32 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>>>>> without starting tramp
>>>>> I do not know what that means.
>>>> I mean trying to connect to a remote host via tramp.
>>> So you're saying that Tramp tries to connect to "toto" when you type
>>> "/toto:"?
>> Yes, but that is what we expect. (/toto: should be a valid hostname
>> maybe set in ~/.ssh/config)
>> What we don't want is when you write:
>> /ssh: => tramp try to connect
>
> Does this happen? Where does it connect to?
>
>> /sudo: ==> tramp try to connect
>
> Again, where does Tramp try to connect in this case?
No where, that's the problem.
>> we expect tramp to connect only when we have:
>> /sudo:: and not before (i.e before entering the second ":").
>
> When I do C-x C-f /ssh: TAB Tramp does not try to connect to anything,
> it just shows me some hostname completion.
Because this implementation works for vanilla emacs completion, but is
unusable elsewhere. (like try-completion)
>> But I have no problem here with my code (anything),
>> it seem the problem is in ido and/or icomplete.
>
> I get the same behavior with or without icomplete-mode. I think we need
> you to give us a more specific recipe.
So it's ok if it works, just forget it.
--
Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997
next prev parent reply other threads:[~2011-10-18 5:39 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 17:38 bug#7583: 23.2; ido loads tramp too eagerly Dave Abrahams
2011-10-16 9:00 ` Michael Albinus
2011-10-19 19:31 ` Dave Abrahams
2011-10-26 8:47 ` Michael Albinus
2011-10-26 18:19 ` Dave Abrahams
2011-10-26 18:27 ` Michael Albinus
2011-10-16 18:31 ` Juanma Barranquero
2011-10-16 19:17 ` Thierry Volpiatto
2011-10-16 19:40 ` Michael Albinus
2011-10-16 21:20 ` Thierry Volpiatto
2011-10-17 6:16 ` Thierry Volpiatto
2011-10-17 7:38 ` Michael Albinus
2011-10-17 13:31 ` Stefan Monnier
2011-10-17 14:18 ` Thierry Volpiatto
2011-10-17 15:44 ` Stefan Monnier
2011-10-17 17:02 ` Thierry Volpiatto
2011-10-17 19:36 ` Stefan Monnier
2011-10-18 5:39 ` Thierry Volpiatto [this message]
2011-10-18 13:22 ` Stefan Monnier
2011-10-18 17:01 ` Thierry Volpiatto
2011-10-18 19:04 ` Stefan Monnier
2011-10-19 10:04 ` Michael Albinus
2011-10-19 12:49 ` Stefan Monnier
2011-10-19 20:33 ` Michael Albinus
2011-10-20 13:50 ` Michael Albinus
2011-10-20 14:35 ` Thierry Volpiatto
2011-10-20 18:22 ` Michael Albinus
2011-10-20 18:43 ` Thierry Volpiatto
2011-10-20 18:40 ` Stefan Monnier
2011-10-24 10:17 ` Michael Albinus
2011-10-27 18:29 ` Thierry Volpiatto
2011-10-17 15:10 ` 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=87boteq2nm.fsf@gmail.com \
--to=thierry.volpiatto@gmail.com \
--cc=7583@debbugs.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).