all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Arne Babenhauserheide <arne_bab@web.de>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 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 20:42:29 +0100	[thread overview]
Message-ID: <1958993.WpLuDv5Pkc@fluss> (raw)
In-Reply-To: <877golsyoe.fsf@gmx.de>

[-- Attachment #1: Type: text/plain, Size: 1950 bytes --]

Am Donnerstag, 13. Dezember 2012, 17:29:37 schrieb Michael Albinus:
> Arne Babenhauserheide <arne_bab@web.de> writes:
> > Can’t tramp find out itself, that it is confused?
> 
> Not so easy. There could be good reasons not to connect: timeouts,
> connection interrupts, whatever. Sometimes it is better to let Tramp
> resynchronize.
> 
> For example, there's an ongoing work to integrate mosh into Tramp. This
> would allow to reconnect automatically, even if your laptop has been
> offline for a while, and you have moved from work to home.

That sounds pretty awesome!

> > I can now clean it, but every new user will be pretty confused…
> 
> I know :-( But I have no better recipe.

I think I just found one:

The error I got was:


\ Opening connection for arne@ftp using ssh
Tramp: Opening connection for arne@ftp using ssh...done
byte-code: Process died


Is it possible to adapt that error message so it states:


\ Opening connection for arne@ftp using ssh
Tramp: Opening connection for arne@ftp using ssh...done
byte-code: Process died. If this happens repeatedly, try 

    `M-x tramp-cleanup-this-connection`


That would allow newbies to get out of the loop without killing the buffer.

> Could we agree to close this bug?

I think as long as tramp in the buffer still blocks writes and the user does 
not get told how he can exit the block, the bug still persists and closing it 
would just close the eyes against an existing problem (or worse: look like it 
was fixed without providing a solution).

But if the error could just tell the user how to fix the condition, that would 
suffice for closing the bug, I think: The error condition would no longer 
require new users to kill the buffer.

Does that sound like a reasonable approach to you?

Best wishes,
Arne
-- 
1w6 sie zu achten,
sie alle zu finden,
in Spiele zu leiten
und sacht zu verbinden.
→ http://1w6.org


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 316 bytes --]

  reply	other threads:[~2012-12-13 19:42 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1958993.WpLuDv5Pkc@fluss \
    --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 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.