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 00:24:52 +0100 Message-ID: References: <8334xm7jsm.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="00000000000060826e060947d003" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="24111"; 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 00:25:49 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 1qz3Xx-00064m-9D for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 04 Nov 2023 00:25:49 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qz3Xg-0004JT-7a; Fri, 03 Nov 2023 19:25:32 -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 1qz3Xa-0004HN-Gd for bug-gnu-emacs@gnu.org; Fri, 03 Nov 2023 19:25:26 -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 1qz3Xa-0007k3-8J for bug-gnu-emacs@gnu.org; Fri, 03 Nov 2023 19:25:26 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qz3YA-0004lA-1A for bug-gnu-emacs@gnu.org; Fri, 03 Nov 2023 19:26:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: dalanicolai Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 03 Nov 2023 23:26: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.169905394818275 (code B ref 66922); Fri, 03 Nov 2023 23:26:01 +0000 Original-Received: (at 66922) by debbugs.gnu.org; 3 Nov 2023 23:25:48 +0000 Original-Received: from localhost ([127.0.0.1]:60038 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qz3Xw-0004kg-1R for submit@debbugs.gnu.org; Fri, 03 Nov 2023 19:25:48 -0400 Original-Received: from mail-wm1-x330.google.com ([2a00:1450:4864:20::330]:47420) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qz3Xt-0004kP-Hk for 66922@debbugs.gnu.org; Fri, 03 Nov 2023 19:25:46 -0400 Original-Received: by mail-wm1-x330.google.com with SMTP id 5b1f17b1804b1-4084e49a5e5so22140275e9.3 for <66922@debbugs.gnu.org>; Fri, 03 Nov 2023 16:25:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1699053904; x=1699658704; 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=KdD1ReLsXXtoWxfGV4E2G/O/tmqog4hjzCZXkrN+YMM=; b=MPaI+kG5Zo4ncccG/2mlmhRh+oNtdg48jYNaOGzSw3PqOV2LDY/EvV4a3TxHJIV+nH v4WFtTbUXlGDnMmIORIrl5DQPKHF1IrvrgIFLGF537hiR8nNLAWKzR0imy0pvnL4ObnE KwxsNNGoVw5eTulYZI9afGMC1kzoBLnvXwOncyeJQyMZ84wfPkdGWXpLlKfMMIzsFizw Rewcmg2mtpHziYJ6MoExNyM2BMiSIIdtgLAb5OMOCY2X9bcHebpCxyD2zhDSInH6HzSy DyUQQK03a7Il3QZ7266Xzg24P79Tjf0Vn/QzMomts5haHgorVgLqQGjuIIqyuIAdOPoI +Z3w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699053904; x=1699658704; 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=KdD1ReLsXXtoWxfGV4E2G/O/tmqog4hjzCZXkrN+YMM=; b=H2omDnbHqFl1/EPsqYFrGLiLFW7DyOujjE67ECt8lKqacnYK1QwPZh5fSCo7g6bHMn cpQJ7m1HpN++oR/45Pdrbtd70jyT5ZpqRUtbFMOatmUlMc0XorLq/kPTHCWfUR+IV31E DiNB9nYa8LDnmDyf83t5dmlS+fx0v9CQqjOoT4C4rsoBWIY8Zsd0HwiYAJiUQmD32nlS ppTU96jZd9BeWl69ih6qgRlzkIZsZzWltoQx0lrUYvhw1DoETEpX0DzV4k1+avuEPJ6P w0u0uTeRrbwH5DYkxBv+QDnRQfX63O5oQ30uQypX3oyijfPHhktds1aegGCnA2mHwg1l MRiw== X-Gm-Message-State: AOJu0YxfnD0dmhmGkk+9gG5pp5TXoMNkO6uS5j7+mUhqc3itxeZR4W+Z 7lCDp1EJdP+jml6tknJuSrNy8B78T0FwU0KmsZFZUQyP X-Google-Smtp-Source: AGHT+IGNmDthfEQ64qTPahw6L+i2eGzjb1COmFX1k7X/YRh+h2m2tX5wNADgXl4H9YNEtAEk0HYirjo5AEHTulEVHhY= X-Received: by 2002:a05:600c:1caa:b0:405:1bbd:aa9c with SMTP id k42-20020a05600c1caa00b004051bbdaa9cmr18761433wms.34.1699053903576; Fri, 03 Nov 2023 16:25:03 -0700 (PDT) In-Reply-To: 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:273732 Archived-At: --00000000000060826e060947d003 Content-Type: text/plain; charset="UTF-8" Therefore, sending it again to all On Sat, 4 Nov 2023 at 00:23, dalanicolai wrote: > (Sorry, I used the wrong reply button) > > 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). > > (Also obviously, I can not use a normal print/message, when > 'investigating' redisplay issues) > > The documentation says that redisplay should recalculate the > window-start, and that by using force-window-update, we can ensure > that some buffer or window gets redisplayed on the next redisplay. > > Now if you evaluate the code, from the bug report in GUI emacs, and > look at the last output printed to the terminal, it shows that the > window-start is still at 1, while it should be at 11, because I > applied the 'force-window-update' incl. the redisplay after the > (goto-char 11). > > Is there something I am not understanding correctly? Or could I > consider it a bug in the documentation? As far as I know, I checked > the documentation and the behavior quite rigidly. > > On Fri, 3 Nov 2023 at 19:50, Eli Zaretskii wrote: > >> > From: dalanicolai >> > Date: Fri, 3 Nov 2023 19:07:47 +0100 >> > >> > I was trying to debug my 'image roll' package, that provides a 'virtual >> > scroll' for displaying documents (i.e. books), when I encountered the >> > following 'bug'. To reproduce it from emacs -Q, just evaluate the >> > following code and press `C-c e`; note that relevant debugging output >> > will be printed to the terminal: >> >> The problem only happens in "emacs -nw", not on a GUI frame. And I >> wonder why you consider this a bug. I think external-debugging-output >> is documented to print to stderr, so the "mess-up" is expected. I'd >> say "don't do that". >> > --00000000000060826e060947d003 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Therefore, sending it again to all

On Sat, 4 Nov 2023 a= t 00:23, dalanicolai <dalanicol= ai@gmail.com> wrote:
(Sorry, I used the wrong reply button)

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 t= o
'external-debugging-output' because the lwarn is what causes t= he
problem. I explained in the bug report that the window-start does not=
get updated when including the lwarn after the forced redisplay (thepoint is at 11, but window-start is still at 1).

(Also obviously, I= can not use a normal print/message, when
'investigating' redisp= lay issues)

The documentation says that redisplay should recalculate= the
window-start, and that by using force-window-update, we can ensure<= br>that some buffer or window gets redisplayed on the next redisplay.
Now if you evaluate the code, from the bug report in GUI emacs, and
lo= ok at the last output printed to the terminal, it shows that the
window-= start is still at 1, while it should be at 11, because I
applied the = 9;force-window-update' incl. the redisplay after the
(goto-char 11).=

Is there something I am not understanding correctly? Or could I
= consider it a bug in the documentation? As far as I know, I checked
the = documentation and the behavior quite rigidly.

On Fri, 3 Nov 2023 at 19= :50, Eli Zaretskii <el= iz@gnu.org> wrote:
> From: dalanicolai <dalanicolai@gmail.com>
> Date: Fri, 3 Nov 2023 19:07:47 +0100
>
> I was trying to debug my 'image roll' package, that provides a= 'virtual
> scroll' for displaying documents (i.e. books), when I encountered = the
> following 'bug'. To reproduce it from emacs -Q, just evaluate = the
> following code and press `C-c e`; note that relevant debugging output<= br> > will be printed to the terminal:

The problem only happens in "emacs -nw", not on a GUI frame.=C2= =A0 And I
wonder why you consider this a bug.=C2=A0 I think external-debugging-output=
is documented to print to stderr, so the "mess-up" is expected.= =C2=A0 I'd
say "don't do that".
--00000000000060826e060947d003--