From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 12872@debbugs.gnu.org
Subject: bug#12872: 24.2; Provide a feature to trigger mode-line redisplay
Date: Sat, 04 Dec 2021 21:26:59 +0200 [thread overview]
Message-ID: <83ee6s5fy4.fsf@gnu.org> (raw)
In-Reply-To: <87mtlg6vzm.fsf@gnus.org> (message from Lars Ingebrigtsen on Sat, 04 Dec 2021 19:55:09 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: 12872@debbugs.gnu.org
> Date: Sat, 04 Dec 2021 19:55:09 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > force-mode-line-update is a blunt weapon, and causes a much more
> > thorough redisplay than its name says. And post-command-hook is not
> > the best method of achieving the desired goal, since it runs after
> > _every_ command, not just a command that changes the line of point.
>
> Perhaps this should be mentioned in the doc string of that function?
It already hints on that. I don't object to saying that more clearly
and explicitly.
But I don't think that's the issue here.
> This function could grow a `mode-line-only' parameter (or value of ALL),
> I guess. Hm... following the logic here isn't trivial. Would setting
> a new flag in the window object that'll make redisplay call
> redisplay_mode_lines be a way to implement this?
We already have the flag. The problem is how to set it only when the
current line changes. I think that's the crux of this issue.
next prev parent reply other threads:[~2021-12-04 19:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 18:27 bug#12872: 24.2; Provide a feature to trigger mode-line redisplay Eli Zaretskii
2012-11-12 19:46 ` Eli Zaretskii
2012-11-12 22:17 ` Drew Adams
2012-11-13 3:57 ` Eli Zaretskii
2012-11-13 15:38 ` Drew Adams
2021-12-04 4:46 ` Lars Ingebrigtsen
2021-12-04 7:54 ` Eli Zaretskii
2021-12-04 18:55 ` Lars Ingebrigtsen
2021-12-04 19:26 ` Eli Zaretskii [this message]
2021-12-04 19:40 ` Lars Ingebrigtsen
2021-12-04 19:43 ` Eli Zaretskii
2021-12-04 22:04 ` Lars Ingebrigtsen
2021-12-05 7:02 ` Eli Zaretskii
2021-12-05 20:05 ` Lars Ingebrigtsen
2021-12-05 20:14 ` Eli Zaretskii
2021-12-06 6:00 ` Lars Ingebrigtsen
2021-12-06 13:02 ` Eli Zaretskii
2021-12-07 20:49 ` Lars Ingebrigtsen
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=83ee6s5fy4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=12872@debbugs.gnu.org \
--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 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.