From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 12872@debbugs.gnu.org
Subject: bug#12872: 24.2; Provide a feature to trigger mode-line redisplay
Date: Sat, 04 Dec 2021 23:04:11 +0100 [thread overview]
Message-ID: <87tufoxc10.fsf@gnus.org> (raw)
In-Reply-To: <83a6hg5f71.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 04 Dec 2021 21:43:14 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> What flag is that?
>
> w->update_mode_line
Oh, I didn't realise that the update_mode_line variable and that field
were separate things...
>> > The problem is how to set it only when the current line changes. I
>> > think that's the crux of this issue.
>>
>> I must admit I didn't understand what was meant by "when the current
>> line changes". 😐
>
> It means point moves from one physical line to another.
Then it doesn't sound difficult to implement that in an efficient
manner? Whatever function Drew is using could just put itself in
post-command-hook and check? Isn't there a line number cache somewhere?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-12-04 22:04 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
2021-12-04 19:40 ` Lars Ingebrigtsen
2021-12-04 19:43 ` Eli Zaretskii
2021-12-04 22:04 ` Lars Ingebrigtsen [this message]
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=87tufoxc10.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=12872@debbugs.gnu.org \
--cc=eliz@gnu.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).