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 09:54:38 +0200 [thread overview]
Message-ID: <83a6hg7qkh.fsf@gnu.org> (raw)
In-Reply-To: <87o85xou2m.fsf@gnus.org> (message from Lars Ingebrigtsen on Sat, 04 Dec 2021 05:46:57 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: 12872@debbugs.gnu.org
> Date: Sat, 04 Dec 2021 05:46:57 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > This is a feature request: provide a way to trigger mode-line
> > redisplay when the current line changes. This is so the mode line
> > could display information about the current line.
> >
> > See the discussion of bug #12867 for more context.
>
> I've skimmed both these bug reports, but I'm still not sure I understand
> the problem. `force-mode-line-update' has existed since forever, I
> think? Doesn't it do what it's supposed to? (And it can be run from
> post-command-hook if that's what Drew wants.)
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.
next prev parent reply other threads:[~2021-12-04 7:54 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 [this message]
2021-12-04 18:55 ` Lars Ingebrigtsen
2021-12-04 19:26 ` Eli Zaretskii
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
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=83a6hg7qkh.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 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).