unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: dalanicolai <dalanicolai@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 66922@debbugs.gnu.org
Subject: bug#66922: 29.1; No redisplay of buffer, even after using `force-window-update'
Date: Sat, 4 Nov 2023 00:23:30 +0100	[thread overview]
Message-ID: <CACJP=3ksD7hCW_22nPPwoT0ZpMT3dbzuNfmki8CxdB=HxE0xvA@mail.gmail.com> (raw)
In-Reply-To: <8334xm7jsm.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1899 bytes --]

(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 <eliz@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
> > 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".
>

[-- Attachment #2: Type: text/html, Size: 2493 bytes --]

  reply	other threads:[~2023-11-03 23:23 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 [this message]
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

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='CACJP=3ksD7hCW_22nPPwoT0ZpMT3dbzuNfmki8CxdB=HxE0xvA@mail.gmail.com' \
    --to=dalanicolai@gmail.com \
    --cc=66922@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).