unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Yuri Khan <yurivkhan@gmail.com>
To: Emacs developers <emacs-devel@gnu.org>
Subject: Flymake, compilation-mode lighters very noisy
Date: Mon, 19 Nov 2018 17:36:10 +0700	[thread overview]
Message-ID: <CAP_d_8W56+VFEFsJ_9Xu6nva0vhxhwFYRPALog=tfxuToTHrrw@mail.gmail.com> (raw)

Hello,

I was fiddling with my Python development environment to start using
python-language-server, and settled on Eglot as a novice-friendly LSP
client.

Now, one side effect of Eglot is that it enables Flymake unconditionally.

Not that I mind, no; actually, I find it very convenient that
potential bugs are highlighted as soon as I create them.

What I do mind, though, is these two menacing eyes staring at me from
the mode line.

    … (Python yas WS SP Flymake[0 0] Projectile[…] ARev ElDoc)
                               ↗   ↖
                bold bright red     bold yellow

(seriously though, I just find bright/high-constrast spots in my
peripheral vision distracting.)

Compilation-mode has the same issue, with as many as four eyes:

    … (Compilation:exit [0] [0 0 0])
                  ↗     ↗   ↗  ↑  ↖
                  green   red  |   green
                             yellow

I understand the motivation: provide instant error, warning and info
counters, and use color coding to avoid having to explain which
counter is for which severity level.

However, I wonder if zero counters could be skipped in the mode line.
After all, they have nothing to say; they shouldn’t be yelling about
that. IMHO.

In the case of compilation-mode, I can redefine the
‘compilation-mode-line-errors’ variable easily enough; it’s just a
mode line fragment referencing a few variables.

Flymake, though, delegates the work to the function
‘flymake--mode-line-format’, which is pretty involved (110 lines of
code). Not much I can do with that, as a user, except copy-pasting
that function into my init.el with a minor change.

Thoughts?



             reply	other threads:[~2018-11-19 10:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-19 10:36 Yuri Khan [this message]
2018-11-20 20:16 ` Flymake, compilation-mode lighters very noisy João Távora
2018-11-21  9:54   ` Yuri Khan
2018-11-21 10:38     ` João Távora
2018-11-21 10:42       ` João Távora
2018-11-21 11:35       ` Yuri Khan
2018-11-21 11:58         ` João Távora
2018-11-21 12:22           ` Yuri Khan
2019-01-05 12:13             ` 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='CAP_d_8W56+VFEFsJ_9Xu6nva0vhxhwFYRPALog=tfxuToTHrrw@mail.gmail.com' \
    --to=yurivkhan@gmail.com \
    --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 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).