From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: =?UTF-8?Q?Cl=c3=a9ment_Pit-Claudel?= Newsgroups: gmane.emacs.devel Subject: Re: questions about correct reveal-mode usage to hide passwords Date: Thu, 11 Jun 2020 13:43:14 -0400 Message-ID: <4973bec9-0abf-8f55-0b60-0879b6fe1fa7@gmail.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="77973"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Jun 11 19:44:36 2020 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 1jjRFk-000KAR-D3 for ged-emacs-devel@m.gmane-mx.org; Thu, 11 Jun 2020 19:44:36 +0200 Original-Received: from localhost ([::1]:51164 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jjRFj-0000LC-Ck for ged-emacs-devel@m.gmane-mx.org; Thu, 11 Jun 2020 13:44:35 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:46940) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jjREd-0007cV-Qe for emacs-devel@gnu.org; Thu, 11 Jun 2020 13:43:27 -0400 Original-Received: from mail-qk1-x72d.google.com ([2607:f8b0:4864:20::72d]:39671) by eggs.gnu.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jjREa-0007bH-0J for emacs-devel@gnu.org; Thu, 11 Jun 2020 13:43:27 -0400 Original-Received: by mail-qk1-x72d.google.com with SMTP id w3so6396529qkb.6 for ; Thu, 11 Jun 2020 10:43:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=cK3nh0YKpw52RQDD8KdLYGX845esebWbkLMISS7JDn8=; b=iPP30xRkiU9Mh2h54XxmIzMfZ1+SonmMUdo3WqdI+s5JPY9mMm8o9VICJ3oJWB2rbg 8QRv9I5K6mt3ggdvXM9YeJ0tqfywGXUIwewMT6hwc9oidv5adkuqkEXZ4a3QrS7Al2yB hbeqqEn/hLhI7Rqo7IFxx06sAE9GqR15seEseLlO7Vwc+EtZ1l4G9bHHRxXVLXO5VrIG 9XN07tv6d8vETSAJvmgW6fQwQxQOtQiyKjAmc5wgZRZuzdjLydC6mYyLHKOtf/IxSLIG RdyfodKGsD3E+oB128Zix0oYuajQ1Abk2BLVdHE7rsLw7D0ID8xFyjHiovs1UaihGKux S40Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=cK3nh0YKpw52RQDD8KdLYGX845esebWbkLMISS7JDn8=; b=l+T4cu657kQ15kqxwqNkUXPLi5vxUmlJgQ7wEYhcN9ZliiCAOAq/wJSymNtLkAn3KK oNy0Hqp8lRM7nQ55mwD8OEAaJhr1r7FvpTImyH7paeJUHLJ5IbBsMA7NxhT2b7m33ADc gCpXCKcvpTc6u7Ks6/vOxo6P3cYtlvI2ewvIMbLeafLzDiHo7ricx5RlTCQIL0qSyihp O6wy1kHBD0/CTgF8GkTtQJLGAMthl+hcpcLhk4B7cI2Wgv9hPs2pMjQASY+C6awKeTjb Qs71IEhE0d8loE+9TCPVO9H9h6MjMdpxTWh+lLOyoqrXZyLXJ6OzCqOVrRr9y0QEV6ek W/dQ== X-Gm-Message-State: AOAM533bhUoztbnJdXfclDv6PAIFmQ4qOQ+cdYs+10rqHd4GTRQyjXRr WjvkqFpjrCd/39XlGi1/VE6TqJS+ X-Google-Smtp-Source: ABdhPJz6Fe/ZVkZYSB5U4AKJDb1oz+UuAtPICJHstuk59180QEwf4UGqe6/bBSpO1qlkFjzJNqdhLA== X-Received: by 2002:a37:4594:: with SMTP id s142mr9506984qka.183.1591897396789; Thu, 11 Jun 2020 10:43:16 -0700 (PDT) Original-Received: from ?IPv6:2601:184:4180:66e7:7d16:396:5437:aae1? ([2601:184:4180:66e7:7d16:396:5437:aae1]) by smtp.googlemail.com with ESMTPSA id l69sm2786209qke.112.2020.06.11.10.43.16 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 11 Jun 2020 10:43:16 -0700 (PDT) In-Reply-To: Content-Language: en-GB Received-SPF: pass client-ip=2607:f8b0:4864:20::72d; envelope-from=cpitclaudel@gmail.com; helo=mail-qk1-x72d.google.com X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=_AUTOLEARN X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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:252124 Archived-At: On 11/06/2020 13.33, Stefan Monnier wrote: >>> One[1] uses font-lock mode to adapt to >>> change dynamically, which works well for live editing, but you can't see >>> the password when you're editing it. >> font-lock is the perfect way to implement this, and it should be easy to > > I'd recommend using jit-lock rather than font-lock. > It might be a case of bikeshedding, but I think it will be both easier > to implement and more robust. Hmm. I meant font-lock-keywords and text properties (which will benefit from jit-lock, of course), rather than hooking up directly into jit-lock and using overlays. Is there something wrong with the text-properties approach?