From: Filippo Argiolas <filippo.argiolas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Foreground color opacity
Date: Tue, 12 Sep 2023 07:24:45 +0200 [thread overview]
Message-ID: <CAOdrLG+3pJf4bdsnGQ1-gY0Nch_QiJ_HpX-hohXiW5gir+yBhw@mail.gmail.com> (raw)
In-Reply-To: <CAOdrLGLO2s7y2ywFQ0XpzwXA53=9Siu6nxqUpjutMiP=MHmC0w@mail.gmail.com>
On Tue, Sep 12, 2023 at 6:55 AM Filippo Argiolas
<filippo.argiolas@gmail.com> wrote:
> > My point is that this technique _will_ break features, and I don't
> > think it's reasonable to expect each one of them to be fixed
> > individually.
>
> Sure and that's a pretty valid point. Thank you for the insight!
> I could experiment a bit more with overlays. Maybe setting an overlay
> for each node instead of directly changing the face property.
FYI, found another potential source of breakage in cc-mode.el
`c-before-change' that looks at the face properties instead of redoing
syntax analysis. Nothing too impactful according to the comments
there, but you're right about font-lock faces being sometimes used to
infer node types.
prev parent reply other threads:[~2023-09-12 5:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 10:45 Foreground color opacity Filippo Argiolas
2023-09-11 12:58 ` Eli Zaretskii
2023-09-11 13:09 ` Filippo Argiolas
2023-09-11 14:04 ` Eli Zaretskii
2023-09-11 14:58 ` [External] : " Drew Adams
2023-09-11 16:08 ` Filippo Argiolas
2023-09-11 16:25 ` Filippo Argiolas
2023-09-11 16:56 ` Eli Zaretskii
2023-09-11 19:00 ` Filippo Argiolas
2023-09-12 2:21 ` Eli Zaretskii
2023-09-12 4:55 ` Filippo Argiolas
2023-09-12 5:24 ` Filippo Argiolas [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOdrLG+3pJf4bdsnGQ1-gY0Nch_QiJ_HpX-hohXiW5gir+yBhw@mail.gmail.com \
--to=filippo.argiolas@gmail.com \
--cc=eliz@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.