From: Protesilaos Stavrou <info@protesilaos.com>
To: "João Távora" <joaotavora@gmail.com>
Cc: 44689@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#44689: 28.0.50; Use appropriate face for Flymake unknown backend
Date: Wed, 18 Nov 2020 07:58:51 +0200 [thread overview]
Message-ID: <87y2izxl2c.fsf@protesilaos.com> (raw)
In-Reply-To: <87lff0j67w.fsf@gmail.com> ("João Távora"'s message of "Tue, 17 Nov 2020 16:30:59 +0000")
On 2020-11-17, 16:30 +0000, João Távora <joaotavora@gmail.com> wrote:
>> [...]
>>
>> just to point out that the "?" is easy to get.
>>
>> On 'emacs -Q':
>>
>> (require 'flymake)
>> (setq flymake-start-on-flymake-mode nil)
>>
>> Now visit an '*.el' file. Activate 'flymake-mode' and check the
>> modeline.
>
> Indeed, that's not a misconfiguration. But I'd say it's an edge case:
> normally one does want to start checking when enabling flymake, I just
> kept that option there for backward compatibility. I personally see no
> use for it, do you?
The fact that the option exists means that some people might be using
it. Is there any immediate downside to keeping it around? Personally,
I am fine with any decision you may take and agree that it is not what
one would normally expect when activating 'flycheck-mode'.
What I wanted to suggest when I opened this issue is merely this: if
this "edge case" option remains present, please consider reviewing the
face it uses (with 'mode-line-emphasis' being more appropriate than
'mode-line').
--
Protesilaos Stavrou
protesilaos.com
next prev parent reply other threads:[~2020-11-18 5:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 17:17 bug#44689: 28.0.50; Use appropriate face for Flymake unknown backend Protesilaos Stavrou
2020-11-16 22:20 ` Lars Ingebrigtsen
2020-11-17 5:38 ` Protesilaos Stavrou
2020-11-17 9:20 ` João Távora
2020-11-17 9:47 ` Protesilaos Stavrou
2020-11-17 16:30 ` João Távora
2020-11-18 5:58 ` Protesilaos Stavrou [this message]
2020-11-18 8:29 ` João Távora
2020-11-24 5:23 ` Lars Ingebrigtsen
2020-11-24 5:18 ` Lars Ingebrigtsen
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=87y2izxl2c.fsf@protesilaos.com \
--to=info@protesilaos.com \
--cc=44689@debbugs.gnu.org \
--cc=joaotavora@gmail.com \
--cc=larsi@gnus.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.