From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: dalanicolai Newsgroups: gmane.emacs.bugs Subject: bug#66922: 29.1; No redisplay of buffer, even after using `force-window-update' Date: Sat, 4 Nov 2023 12:07:49 +0100 Message-ID: References: <8334xm7jsm.fsf@gnu.org> <83r0l656ui.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000636111060951a24b" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="29253"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 66922@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Nov 04 12:08:47 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qzEWF-0007NH-83 for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 04 Nov 2023 12:08:47 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qzEW7-0000vO-IA; Sat, 04 Nov 2023 07:08:39 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qzEW0-0000uo-AG for bug-gnu-emacs@gnu.org; Sat, 04 Nov 2023 07:08:33 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qzEVt-0001I6-To for bug-gnu-emacs@gnu.org; Sat, 04 Nov 2023 07:08:32 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qzEWT-0003sA-Us for bug-gnu-emacs@gnu.org; Sat, 04 Nov 2023 07:09:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: dalanicolai Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 04 Nov 2023 11:09:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 66922 X-GNU-PR-Package: emacs Original-Received: via spool by 66922-submit@debbugs.gnu.org id=B66922.169909612714858 (code B ref 66922); Sat, 04 Nov 2023 11:09:01 +0000 Original-Received: (at 66922) by debbugs.gnu.org; 4 Nov 2023 11:08:47 +0000 Original-Received: from localhost ([127.0.0.1]:32991 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qzEWE-0003ra-PE for submit@debbugs.gnu.org; Sat, 04 Nov 2023 07:08:47 -0400 Original-Received: from mail-wm1-x334.google.com ([2a00:1450:4864:20::334]:43336) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qzEWC-0003rJ-3L for 66922@debbugs.gnu.org; Sat, 04 Nov 2023 07:08:45 -0400 Original-Received: by mail-wm1-x334.google.com with SMTP id 5b1f17b1804b1-40907b82ab9so23141005e9.1 for <66922@debbugs.gnu.org>; Sat, 04 Nov 2023 04:08:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1699096082; x=1699700882; darn=debbugs.gnu.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=QKow8QoHeu79jI/Wh85de9HXgFTw3dE+iAlO/UsDVu8=; b=jHLWc/fog8IcuKG5Nujpcws7RX5N/QZvEbid/rLd4iNd/GIve1a0PFLa+WOVk6kW7B GaYx+cDqLwTnzU8XNmmXItnndwRJ6QP6y5dfFboTFJwZ/cX50pHkja/kNdXs67TtxYVj GBtzMiGta5Whb17qQzwSzQkHOnb+A+FqfWPd3WZEBSGDaX+JG8+Fj2LneyVKn/nWQOWk xMizZGN3WZCbYZ7wWJv1L9N/Tw9XC4gfRTil5AGl8gOjwW0vUMULDGFiFgakln/U5p6e Fz1AISZJKGSO8OQ7MyAAOV9wHtRgZ07dAuIM/kUfBNW/4iwmbj0xa1o9ebkwu7UVzLMf 8m9w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699096082; x=1699700882; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=QKow8QoHeu79jI/Wh85de9HXgFTw3dE+iAlO/UsDVu8=; b=luaUtrGe0l/PRo1SUHCEZhr/NNamRv+X7Mg7vj6hY/7K3bSzoESV9/0CrDn3drL600 65rvDMYcCp9qCXr6gnPOwcLswr0Dd2SAJ/Kj29JqcW2ONNAnscNX/KhJpZ2JEJSlbq5Q QKO4FZ765Y+db5l2uZQXj2C/QYoRGWhS2NzyWgGn/ty82JtjnhfVyAiwNTNlZQJg5cZn V9ZzsfksL4UlFQ268XBu7LuN/P3z/iMwSkm2Wg7+eiv8aKLokfPS6H+nPBJxCiwoQuVZ E9FDyDyCgvIRtdjR6j/dtSgv+ksN5RXX/SOHwNdzoDvQ/EIC6ECVABEBrSrxV9Cor4cP W8hA== X-Gm-Message-State: AOJu0YxG65/Nh/7LerTvnxby6SftRRss+nnETeclCx8VToHTfjp2m5a3 mOeGFiuP4gTHn2QSPUcgticdlxZBLKbbDu1WAqsppwO8YK0= X-Google-Smtp-Source: AGHT+IF76484ZW05hyMvFhMKSvDIm+Fg4U1C3R3PZQ7W1jsnVXQrfW3L0jQQVm8zjohDuwHlXqMpQNofKb7ZBHKBBcY= X-Received: by 2002:a05:6000:1a85:b0:32d:dd68:e83 with SMTP id f5-20020a0560001a8500b0032ddd680e83mr5149123wry.21.1699096081685; Sat, 04 Nov 2023 04:08:01 -0700 (PDT) In-Reply-To: <83r0l656ui.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:273773 Archived-At: --000000000000636111060951a24b Content-Type: text/plain; charset="UTF-8" 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! On Sat, 4 Nov 2023 at 08:13, Eli Zaretskii wrote: > > From: dalanicolai > > Date: Sat, 4 Nov 2023 00:23:30 +0100 > > Cc: 66922@debbugs.gnu.org > > > > Sorry Eli, I don't know what you mean here. Over here the problem does > > occur also in the GUI, and I am using the print to > > 'external-debugging-output' because the lwarn is what causes the > > problem. I explained in the bug report that the window-start does not > > get updated when including the lwarn after the forced redisplay (the > > point is at 11, but window-start is still at 1). > > Sorry, I didn't understand what you considered a "bug", because your > original description has all but drowned that in the long description > of what the code does. So I thought that "messes redisplay" is the > problem, and that it alludes to the text from > external-debugging-output that appears inside the window of the TTY > frame. > > If your problem is with window-start, then the reason for that is > simple: lwarn pops up the *Warnings* buffer, so the call to > window-start returns the value for that buffer, not for the "example" > buffer. If, after running the recipe, you do > > C-x b RET > M-: (window-start) RET > > you will see that window-start in "example" is 11, as you expect. > > So I see no bug here. > > > (Also obviously, I can not use a normal print/message, when > > 'investigating' redisplay issues) > > Of course, you can: use 'message', and then look in the *Messages* > buffer. > --000000000000636111060951a24b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thank you for looking again at it Eli,

in the recip= e, I am printing the buffer-name and the window-start
together (where th= e 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 cas= e, indeed, it shows that the selected-window is that of the
warning buff= er.

Finally, I understand now that the current-buff= er 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!

On Sat, 4 Nov 2023 at 08:13, Eli Zaretskii <eliz@gnu.org> wrote:
> From: dalanicolai <dalanicolai@gmail.com>
> Date: Sat, 4 Nov 2023 00:23:30 +0100
> Cc: 66922@d= ebbugs.gnu.org
>
> Sorry Eli, I don't know what you mean here. Over here the problem = does
> occur also in the GUI, and I am using the print to
> 'external-debugging-output' because the lwarn is what causes t= he
> problem. I explained in the bug report that the window-start does not<= br> > get updated when including the lwarn after the forced redisplay (the > point is at 11, but window-start is still at 1).

Sorry, I didn't understand what you considered a "bug", becau= se your
original description has all but drowned that in the long description
of what the code does.=C2=A0 So I thought that "messes redisplay"= is the
problem, and that it alludes to the text from
external-debugging-output that appears inside the window of the TTY
frame.

If your problem is with window-start, then the reason for that is
simple: lwarn pops up the *Warnings* buffer, so the call to
window-start returns the value for that buffer, not for the "example&q= uot;
buffer.=C2=A0 If, after running the recipe, you do

=C2=A0 C-x b RET
=C2=A0 M-: (window-start) RET

you will see that window-start in "example" is 11, as you expect.=

So I see no bug here.

> (Also obviously, I can not use a normal print/message, when
> 'investigating' redisplay issues)

Of course, you can: use 'message', and then look in the *Messages*<= br> buffer.
--000000000000636111060951a24b--