From: Arne Babenhauserheide <arne_bab@web.de>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Arne Babenhauserheide <arne_bab@web.de>, 13151@debbugs.gnu.org
Subject: bug#13151: 24.2; tramp with ido: enters self-killing loop when opening /ftp: and hitting enter.
Date: Thu, 13 Dec 2012 15:08:31 +0100 [thread overview]
Message-ID: <87ip86doyo.wl%arne_bab@web.de> (raw)
In-Reply-To: <87mwxis4wi.fsf@gmx.de>
At Thu, 13 Dec 2012 10:00:29 +0100,
Michael Albinus wrote:
> I'm not sure it is a bug what you have detected. Ido and Tramp have
> exactly done what you have asked for. <RET> is bound to
> `ido-exit-minibuffer' (i.e., you have completed file name
> insertion). And ido has even asked you to confirm this. What else do you
> expect?
I would expect that C-x C-w would still work even though I entered a
nonsensical path (probably after hitting C-g to abort).
The bug is not that it tried to open arne@ftp, the bug is that I had
to kill the buffer and reopen the file to be able to use C-x C-w again.
> During these tests, I have found another error in recursive loading of
> Tramp modules, which has been introduced recently. This one I could fix.
>
> For the bug report, I believe I cannot do anything else. So I would like
> to close it, if you don't oppose.
If the recursive loading fix fixes the issue that C-x C-f does not
work anymore, then sure. Otherwise I think it would be better to keep
it open…
> …
> I have no other proposal what to change; ido's internal
> mechanery seems to work well wrt remote files.
Yepp, generally it is really nice!
Thank you for working on it!
Best wishes,
Arne
next prev parent reply other threads:[~2012-12-13 14:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 0:16 bug#13151: 24.2; tramp with ido: enters self-killing loop when opening /ftp: and hitting enter Arne Babenhauserheide
2012-12-12 12:15 ` Michael Albinus
2012-12-12 15:43 ` Arne Babenhauserheide
2012-12-13 9:00 ` Michael Albinus
2012-12-13 14:08 ` Arne Babenhauserheide [this message]
2012-12-13 15:52 ` Michael Albinus
2012-12-13 16:01 ` Arne Babenhauserheide
2012-12-13 16:29 ` Michael Albinus
2012-12-13 19:42 ` Arne Babenhauserheide
2012-12-13 21:12 ` Michael Albinus
2012-12-15 2:16 ` Arne Babenhauserheide
2012-12-16 10:53 ` Michael Albinus
2012-12-18 13:38 ` Michael Albinus
2012-12-18 14:37 ` Arne Babenhauserheide
2012-12-18 15:47 ` Michael Albinus
2012-12-15 13:32 ` Arne Babenhauserheide
2012-12-18 13:57 ` bug#13151: control message for bug #13151 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=87ip86doyo.wl%arne_bab@web.de \
--to=arne_bab@web.de \
--cc=13151@debbugs.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 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).