From: Michael Albinus <michael.albinus@gmx.de>
To: Spencer Baugh <sbaugh@janestreet.com>
Cc: 63539@debbugs.gnu.org
Subject: bug#63539: 29.0.90; TRAMP fails to detect shell prompts containing ]
Date: Tue, 16 May 2023 19:53:27 +0200 [thread overview]
Message-ID: <877ct8w4bs.fsf@gmx.de> (raw)
In-Reply-To: <ierttwcp6vs.fsf@janestreet.com> (Spencer Baugh's message of "Tue, 16 May 2023 12:40:07 -0400")
Spencer Baugh <sbaugh@janestreet.com> writes:
Hi Spencer,
> Attempting to ssh to a machine with a prompt like:
>
> [user@hostname] foo/bar/path $
>
> will hang, because TRAMP thinks that the prompt ends at the "]", not the
> "$".
>
> I guess this is because TRAMP supports prompts like "[foo bar baz]" with
> no trailing $. And it isn't greedy when reading the prompt, so it stops
> at the first "]".
>
> One can work around this by configuring the machine's prompt, but []
> seem relatively common in prompts (in my personal experience), and it
> would be nice if this worked by default. (So far I've only seen [] in
> custom prompts but there are probably some OSs/distributions with [] in
> their prompt by default)
What's wrong with the recipe for your remote .profile:
--8<---------------cut here---------------start------------->8---
[[ $TERM == "dumb" ]] && PS1='$ ' && return
--8<---------------cut here---------------end--------------->8---
The Tramp manual gives an extended version of the recipe, which handles
also the zsh line editing problem, but you see the idea.
And there is also the user option `tramp-shell-prompt-pattern' which you
can customize as you like.
Note, that Tramp cannot handle any case a user would prefer for
detecting the prompt.
Best regards, Michael.
next prev parent reply other threads:[~2023-05-16 17:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 16:40 bug#63539: 29.0.90; TRAMP fails to detect shell prompts containing ] Spencer Baugh
2023-05-16 17:53 ` Michael Albinus [this message]
2023-05-16 19:28 ` Spencer Baugh
2023-05-16 20:06 ` Spencer Baugh
2023-05-17 14:07 ` Michael Albinus
2023-05-17 14:59 ` Spencer Baugh
2023-05-17 15:39 ` Michael Albinus
2023-05-17 16:56 ` Michael Albinus
2023-05-17 17:28 ` Michael Albinus
2023-05-17 18:08 ` Spencer Baugh
2023-05-17 18:41 ` Michael Albinus
2023-05-18 15:49 ` Michael Albinus
2023-05-20 10:18 ` Michael Albinus
2023-05-22 17:30 ` Spencer Baugh
2023-05-22 19:17 ` Michael Albinus
2023-05-22 19:45 ` Spencer Baugh
2023-05-23 13:49 ` Michael Albinus
2023-05-23 14:34 ` Spencer Baugh
2023-05-23 16:31 ` Michael Albinus
2023-05-25 7:36 ` Michael Albinus
2023-05-17 13:53 ` Michael Albinus
2023-05-17 14:04 ` Spencer Baugh
2023-05-17 14:12 ` 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=877ct8w4bs.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=63539@debbugs.gnu.org \
--cc=sbaugh@janestreet.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 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).