From: Michael Albinus <michael.albinus@gmx.de>
To: Chris Thompson <teaforthecat@gmail.com>
Cc: 14808-done@debbugs.gnu.org
Subject: bug#14808: 24.3; Tramp hangs on unmatched prompt pattern
Date: Mon, 15 Jul 2013 14:15:59 +0200 [thread overview]
Message-ID: <87vc4cdnnk.fsf@gmx.de> (raw)
In-Reply-To: <CAOP1k=_QKxCxuPTAtYQK1zkeBSQEWA5nYd+y35hGZeNphoUGXw@mail.gmail.com> (Chris Thompson's message of "Mon, 15 Jul 2013 06:38:02 -0500")
Chris Thompson <teaforthecat@gmail.com> writes:
Hi Chris,
> I successfully replicated your work. I see the message in the
> minibuffer:
[...]
That's the intention of my change. You shall get more information where
to look for.
> The value of tramp-shell-prompt-pattern:
> "\\(?:^\\|\n \\)[^]#$%>\n]*#?[]#$%>] *\\(\\[[0-9;]*[a-zA-Z] *\\)*"
>
> When I add a colon to the list of ending characters in that regex,
> which would be #:$%>, then opening the file with sudo works
> beautifully. (because of the PS1 value which is set in
> .../root/.bashrc)
We have kept out the trailing colon in `tramp-shell-prompt-pattern',
because often you get information or requests during login with such a
trailing colon, which should not be recognized as prompt. Like this:
Password:
So from my pov, this bug is resolved. I recommend you to use a prompt
w/o a trailing colon. Or you modify `tramp-shell-prompt-pattern', as you
have done.
> Thanks,
> Chris
Best regards, Michael.
prev parent reply other threads:[~2013-07-15 12:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-06 22:10 bug#14808: 24.3; Tramp hangs on unmatched prompt pattern Chris Thompson
2013-07-09 13:50 ` Michael Albinus
2013-07-10 15:01 ` Michael Albinus
2013-07-11 10:01 ` Michael Albinus
[not found] ` <CAOP1k=-xDLrSbx380Gw98GsXb_7z-=sVrXtJVaKKxabKixNe-w@mail.gmail.com>
[not found] ` <CAOP1k=_QKxCxuPTAtYQK1zkeBSQEWA5nYd+y35hGZeNphoUGXw@mail.gmail.com>
2013-07-15 12:15 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vc4cdnnk.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=14808-done@debbugs.gnu.org \
--cc=teaforthecat@gmail.com \
/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.