From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: [Patch] Avoid recording chars when reading passwords Date: Tue, 14 Jun 2022 08:34:22 -0400 Message-ID: References: <87edzz8dzo.fsf@elite.giraud> <834k0v5f7z.fsf@gnu.org> <8735g7vb47.fsf@elite.giraud> <83bkuvtr3q.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4392"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: Manuel Giraud , emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Jun 14 14:37:23 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o15nM-0000qP-A7 for ged-emacs-devel@m.gmane-mx.org; Tue, 14 Jun 2022 14:37:20 +0200 Original-Received: from localhost ([::1]:50008 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o15nL-0007M1-1H for ged-emacs-devel@m.gmane-mx.org; Tue, 14 Jun 2022 08:37:19 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:50608) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o15kc-00048V-EO for emacs-devel@gnu.org; Tue, 14 Jun 2022 08:34:30 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:34724) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o15kZ-0002GL-Tl; Tue, 14 Jun 2022 08:34:29 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id AB75744025B; Tue, 14 Jun 2022 08:34:25 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 2FA254414AF; Tue, 14 Jun 2022 08:34:24 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1655210064; bh=fCOFhUuf2STgzCssgsbAeZSaIbEreJFsccJSsU85Y2A=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=J9dWLzjGiTo8EBUdfRPFbPOGiNET+qWaUwWcrKEwMAbvCUS3swiW0Pf09UTq0bIcL XVWpmswwnt/hTr6K/ykpPVranhKXniIFRFJzAE76MxECDxjXU/D2kPndLn6wbHmIfa P3rBcuALJmTCzMCs3P9FB3ncaCO5tlJzuvIEyCn7c4s22G6inlAuGQ6PUKYov7mzA/ ado2+wibSTH1cPEk12JwsvZxZLgD3nnTB5Vi4dHJtN8mhLh2EZUoBSIiKJxWLbg4Ui nkCcYL40w/5xK4QytNHlG/t11pGrOelXF0TMnAYZwvvFfN5RYuEAliiZJnnV1Sf7Ht wYciG4YeSCEwQ== Original-Received: from pastel (unknown [45.72.221.51]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id F3F6D12022C; Tue, 14 Jun 2022 08:34:23 -0400 (EDT) In-Reply-To: <83bkuvtr3q.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 14 Jun 2022 14:35:37 +0300") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:291174 Archived-At: Eli Zaretskii [2022-06-14 14:35:37] wrote: > Stefan, do you see any way of producing (no-record . CH) from "normal" > input APIs, for reading input that shouldn't be echoed or recorded? No: the (no-record . CH) is specific to `unread-command-events`, i.e. to events that are "synthesized" (typically from previously read events) whereas those events that come from the keyboard get added directly to the lossage buffer before we have a chance to do anything about it. > If not, we will resurrect that variable and use it instead. Sounds good to me. Stefan