GNU bug report logs - #38181
Actual height of mode-line not taken into account

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: martin rudalics <rudalics <at> gmx.at>
Cc: jonas <at> bernoul.li, 38181 <at> debbugs.gnu.org
Subject: Re: bug#38181: Actual height of mode-line not taken into account
Date: Thu, 07 May 2020 15:41:59 +0300

> Cc: jonas <at> bernoul.li, 38181 <at> debbugs.gnu.org
> From: martin rudalics <rudalics <at> gmx.at>
> Date: Thu, 7 May 2020 10:34:40 +0200
> 
>  >> I simply don't yet understand why updating the frame decorations that have nothing to do with text layout needs init_iterator to run.  What am I missing?  Redisplay doesn't in general redraw the whole frame, it only redraws windows.
>  >
>  > Answering my own question: because the clear_under_internal_border
>  > method, which redraws the internal border, is called from
>  > redisplay_internal.
> 
> That's only a secondary issue, I think.  clear_under_internal_border is
> called from so many places.  The real reason is, as I tried to explain
> before, to update the basic faces, however that is accomplished.

What puzzled me was how init_iterator was involved: without its being
called at least once, the call to clear_under_internal_border will not
use the updated faces.

Previous Next

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