GNU bug report logs - #35523
26.1.92; Please add "PIN" to password-word-equivalents

Previous Next

Full log

Message #11 received at 35523 <at> debbugs.gnu.org (full text, mbox):

From: "Basil L. Contovounesios" <contovob <at> tcd.ie>
To: Noam Postavsky <npostavs <at> gmail.com>
Cc: Eric Hanchrow <eric.hanchrow <at> gmail.com>, 35523 <at> debbugs.gnu.org
Subject: Re: bug#35523: 26.1.92; Please add "PIN" to password-word-equivalents
Date: Wed, 01 May 2019 15:21:25 +0100

Noam Postavsky <npostavs <at> gmail.com> writes:

> Eric Hanchrow <eric.hanchrow <at> gmail.com> writes:
>
>> In related news: it's surprisingly difficult to control this behavior by
>> simply customizing password-word-equivalents; afaict, that variable has
>> an effect only when comint.el loads, which appears to happen before my
>> custom file gets loaded.
>
> You could try loading your custom file earlier, or loading comint
> later.  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)))))

Would the function custom-reevaluate-setting be of use here?

-- 
Basil

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.