unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: dalanicolai <dalanicolai@gmail.com>
Cc: 66922-done@debbugs.gnu.org
Subject: bug#66922: 29.1; No redisplay of buffer, even after using `force-window-update'
Date: Sat, 04 Nov 2023 13:17:43 +0200	[thread overview]
Message-ID: <83ttq14vjc.fsf@gnu.org> (raw)
In-Reply-To: <CACJP=3=Cf5DA6B7dn3O2d=48FyC9ZN6fV_i7P2eR0ZGsop0d=g@mail.gmail.com> (message from dalanicolai on Sat, 4 Nov 2023 12:07:49 +0100)

> From: dalanicolai <dalanicolai@gmail.com>
> Date: Sat, 4 Nov 2023 12:07:49 +0100
> Cc: 66922@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.





      reply	other threads:[~2023-11-04 11:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-03 18:07 bug#66922: 29.1; No redisplay of buffer, even after using `force-window-update' dalanicolai
2023-11-03 18:50 ` Eli Zaretskii
2023-11-03 23:23   ` dalanicolai
2023-11-03 23:24     ` dalanicolai
2023-11-04  7:13     ` Eli Zaretskii
2023-11-04 11:07       ` dalanicolai
2023-11-04 11:17         ` Eli Zaretskii [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83ttq14vjc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=66922-done@debbugs.gnu.org \
    --cc=dalanicolai@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).