unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 56184-done@debbugs.gnu.org
Subject: bug#56184: 29.0.50; Increasing max-redisplay-ticks after it is set very low does nothing
Date: Sat, 25 Jun 2022 08:02:51 +0800	[thread overview]
Message-ID: <87y1xlehjo.fsf@yahoo.com> (raw)
In-Reply-To: <83bkuichpm.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 24 Jun 2022 16:29:57 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Po Lu <luangruo@yahoo.com>
>> Cc: 56184@debbugs.gnu.org
>> Date: Fri, 24 Jun 2022 21:08:15 +0800
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>> > What do you expect it to do?
>> 
>> To redraw the entire frame, since max-redisplay-ticks is now
>> sufficiently large.
>
> That won't happen, unless you type C-l or make some change (e.g., type
> a character) into *scratch*, because the buffer *scratch* is marked
> "not to be redisplayed", and the only window on the frame is the
> window showing *scratch*.  So this is the expected and documented
> behavior.

Okay then, so I'm closing this bug.

Thanks.





      reply	other threads:[~2022-06-25  0:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <877d56fj5s.fsf.ref@yahoo.com>
2022-06-24 10:30 ` bug#56184: 29.0.50; Increasing max-redisplay-ticks after it is set very low does nothing Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-24 11:17   ` Eli Zaretskii
2022-06-24 12:01     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-24 12:05       ` Eli Zaretskii
2022-06-24 13:08         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-24 13:29           ` Eli Zaretskii
2022-06-25  0:02             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [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=87y1xlehjo.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=56184-done@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=luangruo@yahoo.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).