From: Eli Zaretskii <eliz@gnu.org>
To: Manuel Giraud <manuel@ledu-giraud.fr>
Cc: akib@disroot.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: [Patch] Avoid recording chars when reading passwords
Date: Mon, 20 Jun 2022 18:52:17 +0300 [thread overview]
Message-ID: <83v8svl4cu.fsf@gnu.org> (raw)
In-Reply-To: <87ilovxsl6.fsf@elite.giraud> (message from Manuel Giraud on Mon, 20 Jun 2022 17:28:05 +0200)
> From: Manuel Giraud <manuel@ledu-giraud.fr>
> Cc: akib@disroot.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org
> Date: Mon, 20 Jun 2022 17:28:05 +0200
>
> Ok. Here is an updated version of the patch.
Thanks. Two minor nits (but you don't have to submit another patch,
this will be fixed when installing):
> +** New user option 'record-all-keys'.
> +If non-nil, this option will force recording of all input keys
> +including in passwords prompt (this was the previous behaviour). It
> +now defaults to NIL and inhibits recording of passwords.
^^^
We use 'nil' (lower-case, without the quotes). Also, the "now" part
is redundant.
> + DEFVAR_BOOL ("record-all-keys", record_all_keys,
> + doc: /* Non-nil means to record all typed keys. When
> +nil, only passwords' keys are not recorded. */);
The first line of a doc string should be a single complete sentence
(for the benefit of help commands, like 'apropos', which only show the
first lines).
next prev parent reply other threads:[~2022-06-20 15:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 13:46 [Patch] Avoid recording chars when reading passwords Manuel Giraud
2022-06-08 15:48 ` Eli Zaretskii
2022-06-13 13:26 ` Manuel Giraud
2022-06-14 9:38 ` Manuel Giraud
2022-06-14 11:35 ` Eli Zaretskii
2022-06-14 12:34 ` Stefan Monnier
2022-06-14 17:46 ` Eli Zaretskii
2022-06-15 7:59 ` Manuel Giraud
2022-06-18 11:16 ` Eli Zaretskii
2022-06-18 11:29 ` Akib Azmain Turja
2022-06-18 11:33 ` Akib Azmain Turja
2022-06-20 9:58 ` Manuel Giraud
2022-06-20 11:28 ` Eli Zaretskii
2022-06-20 15:28 ` Manuel Giraud
2022-06-20 15:52 ` Eli Zaretskii [this message]
2022-06-25 9:35 ` Eli Zaretskii
2022-06-15 12:27 ` Stefan Monnier
2022-06-15 13:27 ` Eli Zaretskii
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=83v8svl4cu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=akib@disroot.org \
--cc=emacs-devel@gnu.org \
--cc=manuel@ledu-giraud.fr \
--cc=monnier@iro.umontreal.ca \
/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).