From: Andrii Kolomoiets <andreyk.mad@gmail.com>
To: 33740@debbugs.gnu.org
Subject: bug#33740: [PATCH] Customizable flymake mode-line indicator
Date: Fri, 14 Dec 2018 11:19:31 +0200 [thread overview]
Message-ID: <C7555631-1D21-4D2E-A937-91E8445016C0@gmail.com> (raw)
Hi,
I would like to hide Flymake label in mode line leaving just counters.
Customizable mode line indicator like in this patch can solve my issue
and can help to those wanting to keep their mode line cleaner.
diff --git a/lisp/progmodes/flymake.el b/lisp/progmodes/flymake.el
index 7b100da..477abdd 100644
--- a/lisp/progmodes/flymake.el
+++ b/lisp/progmodes/flymake.el
@@ -220,6 +220,10 @@ Specifically, start it when the saved buffer is actually displayed."
:version "26.1"
:type 'boolean)
+(defcustom flymake-mode-line-indicator "Flymake"
+ "Mode label in mode-line."
+ :type 'string)
+
(when (fboundp 'define-fringe-bitmap)
(define-fringe-bitmap 'flymake-double-exclamation-mark
(vector #b00000000
@@ -1152,7 +1156,7 @@ default) no filter is applied."
diags-by-type)))
(flymake--backend-state-diags state)))
flymake--backend-state)
- `((:propertize " Flymake"
+ `((:propertize ,(format " %s" flymake-mode-line-indicator)
mouse-face mode-line-highlight
help-echo
,(concat (format "%s known backends\n" (length known))
next reply other threads:[~2018-12-14 9:19 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 9:19 Andrii Kolomoiets [this message]
2019-01-04 20:27 ` bug#33740: [PATCH] Customizable flymake mode-line indicator João Távora
2019-06-22 14:15 ` Štěpán Němec
2019-09-16 22:22 ` Lars Ingebrigtsen
2019-09-17 6:09 ` Eli Zaretskii
2019-09-17 11:57 ` Lars Ingebrigtsen
2019-09-17 12:13 ` Eli Zaretskii
2019-09-17 12:22 ` Lars Ingebrigtsen
2019-09-17 12:44 ` Eli Zaretskii
2019-09-18 13:38 ` Lars Ingebrigtsen
2019-09-18 14:09 ` Lars Ingebrigtsen
2019-09-19 15:28 ` Lars Ingebrigtsen
2019-09-19 15:55 ` Lars Ingebrigtsen
2019-09-19 16:23 ` Lars Ingebrigtsen
2019-09-19 17:26 ` Eli Zaretskii
2019-09-20 12:32 ` Lars Ingebrigtsen
2019-09-20 13:06 ` Eli Zaretskii
2019-09-20 13:13 ` Lars Ingebrigtsen
2019-09-17 14:07 ` João Távora
2019-09-18 13:40 ` Lars Ingebrigtsen
2019-09-18 13:59 ` João Távora
2019-09-19 15:39 ` Lars Ingebrigtsen
2019-09-20 13:07 ` João Távora
2019-09-21 7:54 ` Lars Ingebrigtsen
2019-09-22 20:55 ` Juri Linkov
2019-09-23 9:18 ` João Távora
2019-09-23 18:10 ` Lars Ingebrigtsen
2019-09-23 9:25 ` João Távora
2019-09-23 18:11 ` Lars Ingebrigtsen
2019-09-18 14:02 ` Noam Postavsky
2020-12-29 2:12 ` Lars Ingebrigtsen
2020-12-29 2:19 ` Lars Ingebrigtsen
2020-12-29 13:52 ` João Távora
2020-12-29 14:14 ` Lars Ingebrigtsen
2020-12-29 14:18 ` João Távora
2020-12-29 14:22 ` Lars Ingebrigtsen
2020-12-29 15:13 ` João Távora
2020-12-30 3:22 ` Lars Ingebrigtsen
2020-12-30 9:28 ` João Távora
2020-12-30 20:16 ` Eli Zaretskii
2020-12-30 21:13 ` João Távora
2020-12-31 14:05 ` João Távora
2021-01-01 10:56 ` Lars Ingebrigtsen
2021-01-02 11:27 ` 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=C7555631-1D21-4D2E-A937-91E8445016C0@gmail.com \
--to=andreyk.mad@gmail.com \
--cc=33740@debbugs.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).