From: Michael Albinus <michael.albinus@gmx.de>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-gnu-emacs@gnu.org
Subject: Re: aborting TRAMP / SSH passphrase prompt
Date: Thu, 23 Mar 2017 15:23:47 +0100 [thread overview]
Message-ID: <87mvcct6ks.fsf@detlef> (raw)
In-Reply-To: <87shm4sg17.fsf@elephly.net> (Ricardo Wurmus's message of "Thu, 23 Mar 2017 06:44:52 +0100")
Ricardo Wurmus <rekado@elephly.net> writes:
> Hi list,
Hi Ricardo,
> The problem I had just now was that I was stuck in an unabortable
> password prompt loop.
>
> I’m using Emacs 25.1.1 on a GNU system.
>
> How can something like this be avoided in the future? (Am I just
> holding it wrong?) Should I report this as a bug? It’s hard to
> reproduce this *exactly*, because each time it’s not clear to me how
> *exactly* I got into this mess.
Yes, I would regard this as a bug, pls report it. I will see what could
be done; something like quitting twice (C-g C-g) should bring you out of
the jail.
I cannot promise that a fix will go into the next Emacs 25.x
release. But the next Tramp release, 2.3.2, planned for end of June,
shall fix it.
> Ricardo
Best regards, Michael.
prev parent reply other threads:[~2017-03-23 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 5:44 aborting TRAMP / SSH passphrase prompt Ricardo Wurmus
2017-03-23 14:23 ` Michael Albinus [this message]
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=87mvcct6ks.fsf@detlef \
--to=michael.albinus@gmx.de \
--cc=help-gnu-emacs@gnu.org \
--cc=rekado@elephly.net \
/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.
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).