From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: questions about correct reveal-mode usage to hide passwords
Date: Thu, 11 Jun 2020 13:49:00 -0400 [thread overview]
Message-ID: <jwvy2ota403.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <4973bec9-0abf-8f55-0b60-0879b6fe1fa7@gmail.com> ("Clément Pit-Claudel"'s message of "Thu, 11 Jun 2020 13:43:14 -0400")
>>>> 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?
It's just that using `font-lock-keywords` is fiddly, and then you also
have to set `font-lock-extra-managed-props`, ...
And next thing you know a user wants to use your thing but doesn't want
font-lock coloring, ...
Stefan
next prev parent reply other threads:[~2020-06-11 17:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 14:09 questions about correct reveal-mode usage to hide passwords Ted Zlatanov
2020-06-11 14:21 ` Clément Pit-Claudel
2020-06-11 17:33 ` Stefan Monnier
2020-06-11 17:43 ` Clément Pit-Claudel
2020-06-11 17:49 ` Stefan Monnier [this message]
2020-06-11 18:31 ` Ted Zlatanov
2020-06-11 19:51 ` Stefan Monnier
2020-06-12 16:17 ` Ted Zlatanov
2020-06-12 16:35 ` Clément Pit-Claudel
2020-06-12 17:08 ` Ted Zlatanov
2020-06-16 18:09 ` Ted Zlatanov
2020-06-18 18:38 ` Ted Zlatanov
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=jwvy2ota403.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=cpitclaudel@gmail.com \
--cc=emacs-devel@gnu.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).