all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Yuri Khan <yurivkhan@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Flymake, compilation-mode lighters very noisy
Date: Tue, 20 Nov 2018 20:16:23 +0000	[thread overview]
Message-ID: <CALDnm53dfgZwP0gGiLdRJ__d5EZoVwV4=jE2dy8+2YTyfCcVUA@mail.gmail.com> (raw)
In-Reply-To: <CAP_d_8W56+VFEFsJ_9Xu6nva0vhxhwFYRPALog=tfxuToTHrrw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 854 bytes --]

>
>
>
> 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?
>

Flymake is reasonably new and untested. I'm glad I made eglot a gateway to
testing it and suggesting improvements.

To your point, propose a way to break up that function. What variable and
what semantics would you like to see? Would it be enough for a variable to
state the minimum severity you would want to always see, even with zero
occurance? In your case you would set it somewhere above "error".... If you
read closely you'll find it's now at "warning", though indeed hardcoded.

And let me know over at GitHub how eglot is working out, too...

João

[-- Attachment #2: Type: text/html, Size: 1249 bytes --]

  reply	other threads:[~2018-11-20 20:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-19 10:36 Flymake, compilation-mode lighters very noisy Yuri Khan
2018-11-20 20:16 ` João Távora [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CALDnm53dfgZwP0gGiLdRJ__d5EZoVwV4=jE2dy8+2YTyfCcVUA@mail.gmail.com' \
    --to=joaotavora@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=yurivkhan@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 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.