GNU bug report logs - #64596
30.0.50; On FIXME: in src/buffer.c:1481 (force-mode-line-update)

Previous Next

Full log

Message #230 received at 64596 <at> debbugs.gnu.org (full text, mbox):

From: Ihor Radchenko <yantar92 <at> posteo.net>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: monnier <at> iro.umontreal.ca, 64596 <at> debbugs.gnu.org
Subject: Re: bug#64596: 30.0.50; On FIXME: in src/buffer.c:1481
 (force-mode-line-update)
Date: Mon, 17 Jul 2023 12:00:02 +0000

Eli Zaretskii <eliz <at> gnu.org> writes:

>> This does not help the confusion, unfortunately.
>> Or maybe the terms "redisplay" and "update" should be explained better
>> somewhere near the top of xdisp.c. They clearly have different meaning,
>> but not for untrained eye.
>
> "Update" is the general name of the 3rd step of "redisplay cycle".  It
> takes its name from the function which enters this step: update_frame.

May someone then detail these steps in the top commentary in xdisp.c +
highlight that redisplay term is generally used when deciding if we need
to update. And update is an actual process of putting desired matrix
onto the glass.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.