From: npostavs@gmail.com
To: 35523@debbugs.gnu.org
Cc: Eric Hanchrow <eric.hanchrow@gmail.com>
Subject: bug#35523: 26.1.92; Please add "PIN" to password-word-equivalents
Date: Wed, 01 May 2019 10:31:22 -0400 [thread overview]
Message-ID: <855zqumekl.fsf@gmail.com> (raw)
In-Reply-To: <CAHZoxq9aSm_d-wTNZZ6mk93ronHE8jOh72SYxR93xkT8iX32Fw@mail.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.
next prev parent reply other threads:[~2019-05-01 14:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 12:25 bug#35523: 26.1.92; Please add "PIN" to password-word-equivalents Eric Hanchrow
2019-05-01 12:58 ` Noam Postavsky
2019-05-01 14:21 ` Basil L. Contovounesios
2019-05-01 14:57 ` Eric Hanchrow
2019-05-01 14:57 ` npostavs
2019-05-01 14:31 ` npostavs [this message]
2019-05-04 17:42 ` Noam Postavsky
2019-06-06 23:30 ` Noam Postavsky
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=855zqumekl.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=35523@debbugs.gnu.org \
--cc=eric.hanchrow@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 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.