From: Michael Olson <mwolson@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 4459@emacsbugs.donarmstrong.com, Robin Green <greenrd@greenrd.org>
Subject: bug#4459: 23.1; ERC customize does not hide password from view
Date: Fri, 18 Sep 2009 10:09:31 -0700 [thread overview]
Message-ID: <c8b3bef90909181009k5116f57n89a6d97516dd50e7@mail.gmail.com> (raw)
In-Reply-To: <87my4s1a6j.fsf@stupidchicken.com>
On Fri, Sep 18, 2009 at 9:37 AM, Chong Yidong <cyd@stupidchicken.com> wrote:
>> If I use the Customize mode to set a password for ERC to try
>> automatically, Customize does not hide the password from
>> view. (Incidentally, I can't hide the password from view by clicking
>> the relevant show/hide arrow afterwards, either - it refuses to hide
>> anything.)
>
>> To reproduce this, in ERC major mode (reachable with M-x erc), choose
>> Customize from the ERC menu. Then choose the Erc Services group. Then,
>> under "Erc Nickserv Passwords:", press the INS button and choose some
>> Network name. Press the INS buton under "Nickname and password:" and
>> enter some arbitrary nickname and password. The password is visible on
>> the screen (unlike when ERC prompts for a password itself, when it
>> hides the password by printing periods instead of the actual password
>> characters).
>
> I'm afraid this is not really feasible to fix, because of the way
> Customize is designed.
Would it make sense for me to turn this variable into a defvar instead
of a defcustom, so that users can't accidentally set it in their emacs
init file?
--
Michael Olson || http://mwolson.org/
Projects: Emacs, Muse, ERC, EMMS
next prev parent reply other threads:[~2009-09-18 17:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 16:37 bug#4459: 23.1; ERC customize does not hide password from view Chong Yidong
2009-09-18 17:09 ` Michael Olson [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-17 14:00 Robin Green
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=c8b3bef90909181009k5116f57n89a6d97516dd50e7@mail.gmail.com \
--to=mwolson@gnu.org \
--cc=4459@emacsbugs.donarmstrong.com \
--cc=cyd@stupidchicken.com \
--cc=greenrd@greenrd.org \
/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).