unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Augusto Stoffel <arstoffel@gmail.com>
To: 58141@debbugs.gnu.org
Cc: "João Távora" <joaotavora@gmail.com>
Subject: bug#58141: [Eglot] Default eglot-diagnostic-tag-unnecessary-face is problematic
Date: Sat, 08 Oct 2022 13:15:03 +0200	[thread overview]
Message-ID: <87zge67eiw.fsf@gmail.com> (raw)
In-Reply-To: <87pmffd8ya.fsf@gmail.com> (Augusto Stoffel's message of "Wed, 28 Sep 2022 13:39:25 +0200")

On Wed, 28 Sep 2022 at 13:39, Augusto Stoffel wrote:

> Finally, I think it's hard to be sure the result is readable in all
> custom themes, even all reasonable ones.

I initially wrote this as an abstract argument, but let me point out
that in the Modus Operandi theme (which is eminently reasonable), the
shadow face and font-lock-comment-face are equal.  So it's hard to
distinguish commented-out code from (presumably) unnecessary code.

Here's a concrete suggestion: when a language server diagnostic says
some code is "unnecessary", then apply _both_
eglot-diagnostic-tag-unnecessary-face and the usual Flymake face, with
that order of priority.  If the user so wishes, they can use
eglot-diagnostic-tag-unnecessary-face to override any attribute of the
flymake-* faces.  But, by default, the eglot-diagnostic-tag-* faces are
best kept empty.





  reply	other threads:[~2022-10-08 11:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-28 11:39 bug#58141: [Eglot] Default eglot-diagnostic-tag-unnecessary-face is problematic Augusto Stoffel
2022-10-08 11:15 ` Augusto Stoffel [this message]
2023-02-18 15:00 ` bug#58141: [Eglot] Default eglot-diagnostic-tag-unnecessary-face is problematic' Augusto Stoffel
2023-02-23 11:59   ` João Távora
2023-02-23 18:55     ` Augusto Stoffel
2023-02-23 19:10       ` João Távora

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=87zge67eiw.fsf@gmail.com \
    --to=arstoffel@gmail.com \
    --cc=58141@debbugs.gnu.org \
    --cc=joaotavora@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).