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

Previous Next

Full log

View this message in rfc822 format

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

"Basil L. Contovounesios" <contovob <at> tcd.ie> writes:

> 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?

Yes, that should work (unless there is an unwanted saved-value, I think
that only happens if you've customized and saved during the current
session).

Previous Next

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