From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 43003@debbugs.gnu.org
Subject: bug#43003: 28.0.50; comint-password-prompt-regexp too restrictive
Date: Mon, 24 Aug 2020 14:27:41 +0200 [thread overview]
Message-ID: <878se4dy9u.fsf@gnus.org> (raw)
In-Reply-To: <87pn7hawal.fsf@gmx.net> (Stephen Berman's message of "Sun, 23 Aug 2020 23:26:26 +0200")
Stephen Berman <stephen.berman@gmx.net> writes:
> So this bug report is basically a plea to change the default value of
> comint-password-prompt-regexp to be the same as that of
> eshell-password-prompt-regexp. Or is there a good reason not to do
> this?
The difference is that the former looks for something like "enter"
before something like "password:", while the latter is just looking for
variations of "password:"?
My guess would be that the latter would have more false positives...
but you'd think those would be pretty rare. I can't imagine many people
having shells with prompts like "Type your user name here but definitely
not your password:".
So I think replacing the former with the latter might work, but comint
is very old code, so perhaps it supports older shells better here...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-08-24 12:27 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 [this message]
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
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=878se4dy9u.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=43003@debbugs.gnu.org \
--cc=stephen.berman@gmx.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.
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.