From: Spencer Baugh <sbaugh@janestreet.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 63539@debbugs.gnu.org
Subject: bug#63539: 29.0.90; TRAMP fails to detect shell prompts containing ]
Date: Wed, 17 May 2023 10:59:52 -0400 [thread overview]
Message-ID: <ierzg63nguv.fsf@janestreet.com> (raw)
In-Reply-To: <87sfbvuk4r.fsf@gmx.de> (Michael Albinus's message of "Wed, 17 May 2023 16:07:16 +0200")
Michael Albinus <michael.albinus@gmx.de> writes:
> Spencer Baugh <sbaugh@janestreet.com> writes:
>> But such machines' prompts stop working if they add color, which
>> shell-prompt-pattern also doesn't support (namely that regex doesn't
>> support escape sequences appearing after the prompt, which are necessary
>> to clear the coloring).
>>
>> So actually, how about setting shell-prompt-pattern to the following?
>> All it does is add support for escape characters after the prompt in
>> shell-prompt-pattern. That would make my use case work.
>>
>> (setopt shell-prompt-pattern (rx (* (not (any "#$%>\n")))
>> (any "#$%>")
>> (* blank)
>> ;; Escape characters.
>> (* "^[[" (* (any ";" digit)) alpha (* blank))))
>
> Oh no! There are much more escape sequences but for coloring. We would
> open a can of worms if we start to handle them in Tramp regexps.
Wait, but we already have exactly this kind of regexp for escape
characters in tramp-shell-prompt-regexp. That's where I copied
this regexp from.
next prev parent reply other threads:[~2023-05-17 14:59 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ierzg63nguv.fsf@janestreet.com \
--to=sbaugh@janestreet.com \
--cc=63539@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.