From: Michael Albinus via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Jim Porter <jporterbugs@gmail.com>, 71576@debbugs.gnu.org
Subject: bug#71576: 30.0.50; [PATCH] Improve performance of Comint/Eshell password prompt handling
Date: Sun, 16 Jun 2024 14:29:05 +0200 [thread overview]
Message-ID: <874j9t6pgu.fsf@gmx.de> (raw)
In-Reply-To: <CADwFkm=TvsKTmKH4Fyt0S7g-a0C88wd2+jekBQ+jCXY11WnqoQ@mail.gmail.com> (Stefan Kangas's message of "Sun, 16 Jun 2024 03:53:46 -0700")
Stefan Kangas <stefankangas@gmail.com> writes:
Hi Stefan,
>> +(defcustom comint-password-prompt-max-length 256
>> + "The maximum amount of text to examine when matching password prompts.
>> +When non-nil, only examine the last N characters of a block of output.
>> +If nil, examine all the output.
>> +
>> +This is used by `comint-watch-for-password-prompt' to reduce the amount
>> +of time spent searching for password prompts."
>> + :version "30.1"
>> + :type '(choice natnum
>> + (const :tag "Examine all output" nil))
>> + :group 'comint)
>
> If this is hardcoded in Tramp, are we sure that we need this as an
> option? I'd suggest making it into a defconst or defvar instead.
Tramp uses this value just "by experience", and to be on the safe
side. I can imagine, that people know that prompts are much shorter in
their case, say 25 bytes. A defcustom is OK in my eyes.
(apply #'max (mapcar #'length password-word-equivalents)) => 14
Best regards, Michael.
next prev parent reply other threads:[~2024-06-16 12:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-15 19:50 bug#71576: 30.0.50; [PATCH] Improve performance of Comint/Eshell password prompt handling Jim Porter
2024-06-16 7:45 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-16 10:53 ` Stefan Kangas
2024-06-16 12:29 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-06-17 1:18 ` Jim Porter
2024-06-21 0:42 ` Jim Porter
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=874j9t6pgu.fsf@gmx.de \
--to=bug-gnu-emacs@gnu.org \
--cc=71576@debbugs.gnu.org \
--cc=jporterbugs@gmail.com \
--cc=michael.albinus@gmx.de \
--cc=stefankangas@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 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).