bug#35523: 26.1.92; Please add "PIN" to password-word-equivalents

[npostavs@gmail.com]

[-- Attachment #1: Type: text/plain, Size: 82 bytes --]

[forwarding to list, please use "Reply All" to keep 35523@debbugs.gnu.org on Cc]


[-- Attachment #2: Type: message/rfc822, Size: 1408 bytes --]

From: Eric Hanchrow <eric.hanchrow@gmail.com>
To: Noam Postavsky <npostavs@gmail.com>
Subject: Re: bug#35523: 26.1.92; Please add "PIN" to password-word-equivalents
Date: Wed, 1 May 2019 09:06:02 -0400
Message-ID: <CAHZoxq_y82hEfArHr2PFz0c2RoTvDbWcX0mep8L9=9HEEZvn+Q@mail.gmail.com>

> You could try loading your custom file earlier, or loading comint
> later.

I considered that, but rejected it; it's not blindingly obvious how or
when comint gets loaded, and thus unclear how early I'd need to load
my custom file (nor what else I might break by moving its loading
around).  I fear that juggling the timing like that would become an
endless game of whack-a-mole.

>  Otherwise, you can still avoid the extra load:
>
>     (when (boundp 'comint-password-prompt-regexp)
>       (setq password-word-equivalents
>             '("PIN" "password" "passcode" "passphrase" "pass phrase"))
>       ;; Reset to new standard value.
>       (setq comint-password-prompt-regexp
>             (eval (car (get 'comint-password-prompt-regexp 'standard-value)))))

Aha, that must be deep "defvar" magic.  I'd never heard of
'standard-value before.

I think I'll stick with reloading the whole library; it's clearer to me.

Thanks.