unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Noam Postavsky <npostavs@gmail.com>
Cc: Eric Hanchrow <eric.hanchrow@gmail.com>, 35523@debbugs.gnu.org
Subject: bug#35523: 26.1.92; Please add "PIN" to password-word-equivalents
Date: Wed, 01 May 2019 15:21:25 +0100	[thread overview]
Message-ID: <87y33qw90a.fsf@tcd.ie> (raw)
In-Reply-To: <87imuunxfq.fsf@gmail.com> (Noam Postavsky's message of "Wed, 01 May 2019 08:58:33 -0400")

Noam Postavsky <npostavs@gmail.com> writes:

> Eric Hanchrow <eric.hanchrow@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





  reply	other threads:[~2019-05-01 14:21 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 [this message]
2019-05-01 14:57     ` Eric Hanchrow
2019-05-01 14:57     ` npostavs
2019-05-01 14:31 ` npostavs
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

  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=87y33qw90a.fsf@tcd.ie \
    --to=contovob@tcd.ie \
    --cc=35523@debbugs.gnu.org \
    --cc=eric.hanchrow@gmail.com \
    --cc=npostavs@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).