From: Stephen Berman <stephen.berman@gmx.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 43003@debbugs.gnu.org
Subject: bug#43003: 28.0.50; comint-password-prompt-regexp too restrictive
Date: Mon, 31 Aug 2020 11:26:10 +0200 [thread overview]
Message-ID: <87mu2btbd9.fsf@gmx.net> (raw)
In-Reply-To: <87pn7hawal.fsf@gmx.net>
On Sun, 30 Aug 2020 15:41:57 +0200 Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Stephen Berman <stephen.berman@gmx.net> writes:
>
>> True, I wasn't thinking about that. Then I guess it's best to leave
>> comint-password-prompt-regexp as is and I'll just change it locally.
>> The problem I have with it doesn't seem to be widespread, to say the
>> least. So feel free to close the bug.
>
> OK; done.
A postscript with additional datapoints: In my OP, the the system that
the problem occurs on (Linux From Scratch) uses openssh 8.2p1, while the
system without the problem (an older Linux From Scratch) uses openssh
7.9p1. I've now reproduced the problem on two other GNU/Linux systems:
current openSUSE Tumbleweed, which uses openssh 8.3p1 (and I see the
problem here on two different machines), and openSUSE Leap 15.2, which
uses openssh 8.1p1. This supports my conjecture that the problematic
carriage return in the prompt comes from openssh. If anyone else
running a system with openssh 8.{1,2,3}p1 can reproduce the problem,
then perhaps a different way of handling it than changing the default
value of comint-password-prompt-regexp can be found.
Steve Berman
next prev parent reply other threads:[~2020-08-31 9:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-23 21:26 bug#43003: 28.0.50; comint-password-prompt-regexp too restrictive Stephen Berman
2020-08-24 12:27 ` Lars Ingebrigtsen
2020-08-26 10:10 ` Stephen Berman
2020-08-27 13:02 ` Lars Ingebrigtsen
2020-08-27 15:09 ` Stephen Berman
2020-08-28 14:08 ` Lars Ingebrigtsen
2020-08-28 14:53 ` Stephen Berman
2020-08-30 13:41 ` Lars Ingebrigtsen
2020-08-31 9:26 ` Stephen Berman [this message]
2020-08-31 10:11 ` Robert Pluim
2020-08-31 12:05 ` Stephen Berman
2020-09-01 14:28 ` Lars Ingebrigtsen
2020-09-01 15:03 ` Robert Pluim
2020-09-01 15:06 ` Lars Ingebrigtsen
2020-09-01 15:40 ` Robert Pluim
2020-09-01 16:46 ` Lars Ingebrigtsen
2020-09-01 17:44 ` Robert Pluim
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=87mu2btbd9.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=43003@debbugs.gnu.org \
--cc=larsi@gnus.org \
/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.