From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 48752@debbugs.gnu.org, Ergus <spacibba@aol.com>
Subject: bug#48752: 28.0.50; Feature request: Hook hide-ifdef into font-lock
Date: Mon, 31 May 2021 11:44:01 -0400 [thread overview]
Message-ID: <jwvy2burk0l.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83eedn2jtl.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 31 May 2021 15:01:42 +0300")
> As mentioned on emacs-devel, how exactly to automate this should be
> carefully thought-out, because blindly using the JIT font-lock
> mechanism will cause code blocks to appear and disappear several time
> as long as the user types the preprocessor directive.
When the code is actually made invisible the appear/disappear could be
quite annoying, indeed, but I think Ergus is mostly concerned about the
case where `hide-ifdef-shadow` is activated, where it would make sense
to make it behave like comments and strings, I think.
Stefan
prev parent reply other threads:[~2021-05-31 15:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210530202606.qlopn6lmwzfa75z5.ref@Ergus>
2021-05-30 20:26 ` bug#48752: 28.0.50; Feature request: Hook hide-ifdef into font-lock Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-31 12:01 ` Eli Zaretskii
2021-05-31 14:29 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-31 15:44 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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=jwvy2burk0l.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=48752@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=spacibba@aol.com \
/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).