GNU bug report logs - #66922
29.1; No redisplay of buffer, even after using `force-window-update'

Previous Next

Full log

Message #25 received at 66922-done <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: dalanicolai <dalanicolai <at> gmail.com>
Cc: 66922-done <at> debbugs.gnu.org
Subject: Re: bug#66922: 29.1;
 No redisplay of buffer, even after using `force-window-update'
Date: Sat, 04 Nov 2023 13:17:43 +0200

> From: dalanicolai <dalanicolai <at> gmail.com>
> Date: Sat, 4 Nov 2023 12:07:49 +0100
> Cc: 66922 <at> debbugs.gnu.org
> 
> Thank you for looking again at it Eli,
> 
> in the recipe, I am printing the buffer-name and the window-start
> together (where the buffer-name gets evaluated before window-start),
> and it says that the buffer-name is 'example'. So I expected
> (window-start) to return the window-start from the window displaying
> the example buffer.
> 
> I already wanted to write you that this must be the case, but I
> thought let me first try to print the buffer of the selected-window.
> In that case, indeed, it shows that the selected-window is that of the
> warning buffer. 
> 
> Finally, I understand now that the current-buffer is not per se the same
> as the buffer displayed in the selected window. I understand it now, but
> until now that was not obvious to me.
> 
> Thanks again Eli, for clearing things up!

I'm glad I could be of help.

I'm therefore closing this bug.

Previous Next

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