GNU bug report logs - #29192
26.0.90; flymake-warning's default color might be inappropriate

Previous Next

Package: emacs;

Reported by: Dmitry Gutov <dgutov <at> yandex.ru>

Date: Tue, 7 Nov 2017 14:50:03 UTC

Severity: minor

Found in version 26.0.90

Done: Stefan Kangas <stefan <at> marxist.se>

Bug is archived. No further changes may be made.

Full log


Message #11 received at 29192 <at> debbugs.gnu.org (full text, mbox):

From: Dmitry Gutov <dgutov <at> yandex.ru>
To: Stefan Kangas <stefan <at> marxist.se>
Cc: 29192 <at> debbugs.gnu.org
Subject: Re: bug#29192: 26.0.90; flymake-warning's default color might be
 inappropriate
Date: Tue, 11 Aug 2020 02:25:24 +0300
Hi Stefan,

On 10.08.2020 19:25, Stefan Kangas wrote:
>> But AFAICT, the flymake-warnline face, previously, used DarkOrange (now
>> it's an obsolete alias). Flycheck also uses this color for warnings.
>>
>> Flymake's own fringe indicators (for warning) also use an orange color
>> by default, inheriting it from the `warning' face through
>> `compilation-warning'.
>>
>> So I think that flymake-warning should use it as well.
>>
>> The current blue is pretty and all, but it conveys an optimistic mood,
>> not something I would associate with a warning.
> Make sense.  Could you make that change?

Thank you for the response, but I have warmed up to this new color in 
the years since the change was made. Maybe not very indicative of being 
a warning, it is nevertheless more noticeable than DarkOrange.

Which is a nice property to have.

If you really like the suggestion, I welcome you to play with the color 
change a little. Otherwise, we can just close this.




This bug report was last modified 4 years and 289 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.