From: "João Távora" <joaotavora@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 33740@debbugs.gnu.org, Andrii Kolomoiets <andreyk.mad@gmail.com>
Subject: bug#33740: [PATCH] Customizable flymake mode-line indicator
Date: Wed, 30 Dec 2020 09:28:22 +0000 [thread overview]
Message-ID: <CALDnm50f6wSv1d4SjO402G1w238Wj_abozcowXpiEmk7vL9n4g@mail.gmail.com> (raw)
In-Reply-To: <87ft3oq8pn.fsf@gnus.org>
On Wed, Dec 30, 2020 at 3:22 AM Lars Ingebrigtsen <larsi@gnus.org> wrote:
>
> João Távora <joaotavora@gmail.com> writes:
>
> > How is it more feasible to ask her to write such customizations
> > inside a string than asking her to write the same customizations
> > in a symbolic expression?
>
> Format spec strings is the common idiom for customising display stuff in
> Emacs.
Not all of this "stuff" obviously, only the fraction of it that is trivial.
Case in point, the very commonly customized mode-line.
I appreciate the effort to try to move this along, but if you'd
be more aware of Flymake's mode-line mechanics, you'd
see the format-spec function is underpowered currently
I mean, it _could_ become more powerful. See CL:FORMAT for
example (some love it, some hate it, I respect and use it on
occasion). It could do the job easily, because it has conditional
formatting:
http://www.lispworks.com/documentation/HyperSpec/Body/22_cgb.htm
So, unless format spec grows something similar, it simply isn't the
tool for the job. What growth? See the end of:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=33740#71
in this thread for a possible start.
> > I don't understand your "don't care" comment. You don't care
> > for enhancing format-spec to allow for conditional formattings.
>
> Whether Flymake offers a way to customise the lighter (or not) is up to
> you.
I've started work on a `flymake-mode-line` customizable var, where
users can add and removed pre-baked pieces to control the main
indicator, counters, brackets, etc. If you're interested in enhancing
format-spec, let me know, else I'll continue this approach.
João
next prev parent reply other threads:[~2020-12-30 9:28 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 9:19 bug#33740: [PATCH] Customizable flymake mode-line indicator Andrii Kolomoiets
2019-01-04 20:27 ` 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 [this message]
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=CALDnm50f6wSv1d4SjO402G1w238Wj_abozcowXpiEmk7vL9n4g@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=33740@debbugs.gnu.org \
--cc=andreyk.mad@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 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).