From: Stefan Monnier <monnier@iro.umontreal.ca>
To: martin rudalics <rudalics@gmx.at>
Cc: Juanma Barranquero <lekktu@gmail.com>, 16967@debbugs.gnu.org
Subject: bug#16967: frame related race condition
Date: Mon, 10 Mar 2014 21:33:55 -0400 [thread overview]
Message-ID: <jwvr4697cjf.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <531DB9F3.2030508@gmx.at> (martin rudalics's message of "Mon, 10 Mar 2014 14:11:15 +0100")
> Lately I frequently noticed that an Emacs frame that was for some time
> hidden by other applications and subsequently became exposed by deleting
> their windows was not redrawn and I would like to know whether this was
> the reason. ISTR that others noted the same or a similar misbehavior.
My "redisplay bit" changes of a few months back introduced such bugs.
I haven't seen such problems for a while now, so I think I've caught all
the problems, but maybe I still missed some.
Part of the change is that previously iconified/invisible frames where
redisplayed right away (i.e. their glyph matrices were kept up-to-date),
whereas now they're not. Which means that when they're uniconified or
made visible, we have to first set windows_or_buffers_changed to
REDISPLAY_SOME, to make sure that the subsequent redisplay doesn't
forget to look at them.
Stefan
next prev parent reply other threads:[~2014-03-11 1:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-08 16:19 bug#16967: frame related race condition Juanma Barranquero
2014-03-10 9:04 ` martin rudalics
2014-03-10 10:32 ` martin rudalics
2014-03-10 11:08 ` Juanma Barranquero
2014-03-10 11:45 ` martin rudalics
2014-03-10 12:39 ` Juanma Barranquero
2014-03-10 13:11 ` martin rudalics
2014-03-10 14:48 ` Juanma Barranquero
2014-03-10 19:04 ` martin rudalics
2014-03-10 21:18 ` Juanma Barranquero
2014-03-11 8:07 ` martin rudalics
2014-03-11 21:13 ` Juanma Barranquero
2014-03-12 14:06 ` Stefan Monnier
2014-03-14 11:31 ` martin rudalics
2014-03-14 13:32 ` Stefan Monnier
2014-03-11 1:33 ` Stefan Monnier [this message]
2014-03-11 8:07 ` martin rudalics
2019-10-02 1:47 ` Juanma Barranquero
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvr4697cjf.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=16967@debbugs.gnu.org \
--cc=lekktu@gmail.com \
--cc=rudalics@gmx.at \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.