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

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: rms <at> gnu.org
Cc: yantar92 <at> posteo.net, monnier <at> iro.umontreal.ca, 64596 <at> debbugs.gnu.org
Subject: bug#64596: 30.0.50; On FIXME: in src/buffer.c:1481 (force-mode-line-update)
Date: Fri, 21 Jul 2023 08:48:45 +0300

> From: Richard Stallman <rms <at> gnu.org>
> Cc: eliz <at> gnu.org, monnier <at> iro.umontreal.ca, 64596 <at> debbugs.gnu.org
> Date: Thu, 20 Jul 2023 22:41:01 -0400
> 
>   > Which immediately creates an impression that "redisplay" and "update"
>   > are referring to the same thing.
>   > It would be nice the highlight the distinction rightaway there.
> 
> For me, they are two ways of thinking about the same action.
> Redisplay is a little more terse and a little more technical in feel,
> but concretely it means "updating the screen".

Yes, it does.  "Redisplay" is actually the name of the entire process,
which includes "update_frame" as its last step.

I have modified the commentary in xdisp.c to make this "30KFt view" of
redisplay more clear at first reading.

Previous Next

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