unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: filippo.argiolas@gmail.com, emacs-devel@gnu.org
Subject: Re: [NonGNU ELPA] new package: clangd-inactive-regions
Date: Sun, 03 Nov 2024 07:46:04 +0200	[thread overview]
Message-ID: <86zfmgx42r.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkm=Snf41MS4XMt7LuBC7jnoitks5eSuyKmEomFQG=yPTJw@mail.gmail.com> (message from Stefan Kangas on Sat, 2 Nov 2024 14:52:11 -0700)

> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Sat, 2 Nov 2024 14:52:11 -0700
> Cc: Eli Zaretskii <eliz@gnu.org>
> 
>     As far as I know Emacs doesn't have a way to set foreground text
>     opacity. Best would be a face attribute so that you can set it in an
>     overlay covering each inactive region and be done with
>     it. Unfortunately there is no attribute for this yet.
> 
> Would such a feature be hard to add to the display engine?  Eli?

I don't know the answer, sorry.  Someone who knows how opacity should
be implemented in display back-ends we support should tell.  If this
is going to be a face attribute, we should also decide how to merge
two faces when each one specifies some opacity value.




  parent reply	other threads:[~2024-11-03  5:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-01  9:02 [NonGNU ELPA] new package: clangd-inactive-regions Filippo Argiolas
2024-11-02  9:13 ` Gerd Möllmann
2024-11-03  7:53   ` Filippo Argiolas
2024-11-03  8:43     ` Gerd Möllmann
2024-11-02 21:52 ` Stefan Kangas
2024-11-02 22:35   ` Felician Nemeth
2024-11-03  1:21     ` Stefan Kangas
2024-11-03  8:08       ` Filippo Argiolas
2024-11-03 15:07         ` Stefan Kangas
2024-11-04 17:36       ` Felician Nemeth
2024-11-03  5:59     ` Eli Zaretskii
2024-11-04 17:40       ` Felician Nemeth
2024-11-03  5:46   ` Eli Zaretskii [this message]
2024-11-04  5:34   ` Richard Stallman
2024-11-04  7:17     ` Filippo Argiolas
2024-11-04 12:02       ` Philip Kaludercic
2024-11-05  0:42         ` Filippo Argiolas

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=86zfmgx42r.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=filippo.argiolas@gmail.com \
    --cc=stefankangas@gmail.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).