From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: "Tomas Nordin" <tomasn@posteo.net>,
40888@debbugs.gnu.org, "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Subject: bug#40888: M-x man: don't redraw good pages when not finding bad pages
Date: Wed, 05 Aug 2020 13:28:19 +0200 [thread overview]
Message-ID: <87ft919vsc.fsf@gnus.org> (raw)
In-Reply-To: <CADwFkmmY=zK+SV9VRvf6NMBB2_P-WVL9CWJszZGWmT_TrxnkVA@mail.gmail.com> (Stefan Kangas's message of "Mon, 27 Apr 2020 17:07:40 +0200")
Stefan Kangas <stefan@marxist.se> writes:
>> >>>>> "TN" == Tomas Nordin <tomasn@posteo.net> writes:
>> TN> under the super heading * Lisp Changes in Emacs 26.1.
>> Well all I know is with 26.3,
>> emacs or emacs -nw,
>> I still see a blink (the whole cat man page redrawn) when I do M-x man dog.
>
> I can reproduce this here.
Me too... but I don't think there's a redrawing of the cat page,
really.
What seems to be happening is that M-x man RET dog RET pops up a "*Man
dog*" buffer in a window, and then starts working in the background.
And then it can't find the dog man page, and then kills the buffer (and
window).
This makes everything redisplay, which is the blink we're seeing.
I'm not sure whether anything can be done about this -- it's an artefact
of working asynchronously, and then restoring window configurations.
Anybody got any ideas?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-08-05 11:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 22:59 bug#40888: M-x man: don't redraw good pages when not finding bad pages 積丹尼 Dan Jacobson
2020-04-27 8:33 ` Tomas Nordin
2020-04-27 14:54 ` 積丹尼 Dan Jacobson
2020-04-27 15:07 ` Stefan Kangas
2020-04-27 20:25 ` Tomas Nordin
2020-08-05 11:28 ` Lars Ingebrigtsen [this message]
2020-08-06 5:32 ` 積丹尼 Dan Jacobson
2020-08-06 7:17 ` Lars Ingebrigtsen
2020-08-06 13:40 ` Eli Zaretskii
2020-08-06 17:39 ` 積丹尼 Dan Jacobson
2020-08-06 17:41 ` Lars Ingebrigtsen
2022-02-20 14:17 ` Lars Ingebrigtsen
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=87ft919vsc.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=40888@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
--cc=stefan@marxist.se \
--cc=tomasn@posteo.net \
/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).