From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 36803@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
kevin.legouguec@gmail.com
Subject: bug#36803: 27.0.50; Update mode-line of every window when compilation ends
Date: Fri, 26 Jul 2019 21:35:14 +0200 [thread overview]
Message-ID: <m38sskwpvx.fsf@gnus.org> (raw)
In-Reply-To: <83ef2cmwji.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 26 Jul 2019 22:21:37 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> If the call to force-mode-line-update is the solution you suggest,
> then I think it is not a good solution. We cannot rely in a call to
> force-mode-line-update, because there's the default sentinel, and
> because it's unreasonable to request each sentinel written in Lisp to
> make that call. If every sentinel must do that, then the core should
> do that for them.
Well, when I was looking at where to move the "Compiling"
sort-of-lighter (from out of minor-mode-alist where it didn't belong), I
was looking for other modes that display things in mode lines in all
buffers -- and there doesn't seem to be many.
So while I agree that it seems more logical that this "should just
work", I think the problem is very limited in practice, and having
compile.el (as one of the very few packages that does this) call
force-mode-line-update wouldn't be an outrage.
(Another issue is whether compile.el should do this, and I kinda
think... perhaps not?)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-07-26 19:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 21:22 bug#36803: 27.0.50; Update mode-line of every window when compilation ends Kévin Le Gouguec
2019-07-25 9:42 ` Lars Ingebrigtsen
2019-07-25 10:34 ` Eli Zaretskii
2019-07-25 13:37 ` Kévin Le Gouguec
2019-07-25 14:59 ` Eli Zaretskii
2019-07-26 8:13 ` Eli Zaretskii
2019-07-26 13:59 ` Stefan Monnier
2019-07-26 15:08 ` Eli Zaretskii
2019-07-26 16:23 ` Stefan Monnier
2019-07-26 18:16 ` Eli Zaretskii
2019-07-26 18:53 ` Stefan Monnier
2019-07-26 19:21 ` Eli Zaretskii
2019-07-26 19:35 ` Lars Ingebrigtsen [this message]
2019-07-26 21:26 ` Kévin Le Gouguec
2019-07-27 9:53 ` Lars Ingebrigtsen
2019-07-27 17:01 ` Kévin Le Gouguec
2019-07-27 6:57 ` Eli Zaretskii
2019-07-26 21:10 ` Stefan Monnier
2019-07-27 7:46 ` Eli Zaretskii
2019-07-27 12:46 ` Stefan Monnier
2019-07-27 13:12 ` Eli Zaretskii
2019-07-27 14:00 ` Stefan Monnier
2019-07-27 17:37 ` Kévin Le Gouguec
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=m38sskwpvx.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=36803@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=kevin.legouguec@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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).