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

Previous Next

Package: emacs;

Reported by: Jonas Bernoulli <jonas <at> bernoul.li>

Date: Tue, 12 Nov 2019 16:54:01 UTC

Severity: normal

Fixed in version 29.1

Done: martin rudalics <rudalics <at> gmx.at>

Bug is archived. No further changes may be made.

Full log


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

From: martin rudalics <rudalics <at> gmx.at>
To: Carlos Pita <carlosjosepita2 <at> gmail.com>
Cc: 38181 <at> debbugs.gnu.org
Subject: Re: bug#38181: Actual height of mode-line not taken into account
Date: Sat, 16 Oct 2021 21:41:51 +0200
> I still need to refine my concept of "on window creation". When you say
> "with evert set_window_buffer" I'm not sure whether you mean something
> like:
>
> 1. There is an event (a) of window creation and later and event (b)
> when the buffer is set for the new window. So if I call redisplay
> immediately after (a) it would be too early because the modeline won't
> be properly set up until (b).

Window creation means 'split-window' which assigns the new window a
buffer that appears in the window that was split.

> Or, instead, something like:
>
> 2. Windows often change buffers and buffers may have modeline formats
> that imply different modeline heights.
>
> If 1 is the case then sure, maybe it's a different event that I need
> to listen to, but it's still one forced early redisplay per window.
> But if you mean 2, again I don't see the relevance in practice.

How comes?  'display-buffer-in-side-window' may reuse an existing window
or pop up a new one.  Or do the mode lines of _all_ your windows have
the same height?  That indeed would simplify things a lot.

martin




This bug report was last modified 3 years and 201 days ago.

Previous Next


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