From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 36803@debbugs.gnu.org, larsi@gnus.org, kevin.legouguec@gmail.com
Subject: bug#36803: 27.0.50; Update mode-line of every window when compilation ends
Date: Sat, 27 Jul 2019 08:46:35 -0400 [thread overview]
Message-ID: <jwv8ssjsl6h.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83a7czncm9.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 27 Jul 2019 10:46:38 +0300")
> Yes. And if you add to the recipe yet another, unrelated buffer
> displayed in the 4th window, then its mode line will also show
> "Compiling" if that buffer is not the current buffer when "M-x
> compile" is invoked.
Yes, with 100 windows, 98 of them will stay stale.
> And that brings me right back to the beginning. In response to my
> original question, you said:
>
>> Hmm... AFAIK the "process status" normally only indicates the status of
>> the process running in the buffer to which this mode line belongs.
>> Which is why I made the change to only bset_update_mode_line rather than
>> set the global update_mode_lines.
>
> This is true only if the process status is modified via
> mode-line-process, which is a buffer-local variable. If a Lisp
> program modifies the mode line directly, the result will be global.
> That's what compile.el does via compilation-in-progress, but the most
> basic operation is simply to add %s to mode-line-format (or to
> header-line-format or even to frame-title-format).
That's not a problem: %s only shows the status *of the process in the
current buffer*: the status of a process in buffer A is never
reflected in the %s part of the mode-line of other buffers, which is why
the sentinel code only causes a mode-line update for the process's buffer.
Stefan
next prev parent reply other threads:[~2019-07-27 12:46 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
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 [this message]
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=jwv8ssjsl6h.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=36803@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=kevin.legouguec@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).