From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 69237@debbugs.gnu.org
Subject: bug#69237: 30.0.50; Toggle password visibility
Date: Mon, 19 Feb 2024 18:48:07 +0200 [thread overview]
Message-ID: <86il2kpfi0.fsf@gnu.org> (raw)
In-Reply-To: <87cyssih4g.fsf@gmx.de> (message from Michael Albinus on Mon, 19 Feb 2024 16:54:55 +0100)
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: 69237@debbugs.gnu.org
> Date: Mon, 19 Feb 2024 16:54:55 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> Hi Eli,
>
> > I'm not sure TAB is the best candidate for this. I think it would be
> > better to use some non-character key, like F9 or somesuch. And
> > another one, for keyboards without function key.
>
> As usual, I don't care too much about this, so I'm OK with any
> proposal. However, out of curiosity, what's wrong with TAB? I'm not
> aware that any password contains it.
Is it impossible for TAB to appear in a password? If it is, the TAB
is okay, and my only reservation about that is that TAB is not
generally interpreted in my mental model of "advanced" input patterns
as something that hides/shows stuff. TAB is more about completion and
similar functionality. But that's me.
Let's hear opinions from others.
next prev parent reply other threads:[~2024-02-19 16:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 13:33 bug#69237: 30.0.50; Toggle password visibility Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-18 19:00 ` Eli Zaretskii
2024-02-18 20:04 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-19 12:21 ` Eli Zaretskii
2024-02-19 15:54 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-19 16:48 ` Eli Zaretskii [this message]
2024-02-19 17:08 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-22 22:30 ` Kévin Le Gouguec
2024-02-23 15:43 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-23 16:56 ` Kévin Le Gouguec
2024-02-25 9:11 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-25 10:50 ` Kévin Le Gouguec
2024-02-25 11:25 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-25 13:34 ` Kévin Le Gouguec
2024-02-25 14:09 ` Eli Zaretskii
2024-02-25 14:38 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-25 14:42 ` Eli Zaretskii
2024-02-25 14:48 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-25 15:27 ` Kévin Le Gouguec
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=86il2kpfi0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=69237@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
/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).