From: Juanma Barranquero <lekktu@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: 16967@debbugs.gnu.org
Subject: bug#16967: frame related race condition
Date: Mon, 10 Mar 2014 15:48:29 +0100 [thread overview]
Message-ID: <CAAeL0STVxKir8gTaizHcfXAa-mUuoT0sJyJOxpbZM6q8MjyLyQ@mail.gmail.com> (raw)
In-Reply-To: <531DB9F3.2030508@gmx.at>
On Mon, Mar 10, 2014 at 2:11 PM, martin rudalics <rudalics@gmx.at> wrote:
> should create a normally visible frame f. The fact that this frame has
> its visibility set to zero at the time you `delete-frame' c indicates
> that we have a pretty awful bug.
Yes
> The implications of this are
> substantial because SET_FRAME_VISIBLE has to redisplay_other_windows and
> if that is not done, the consequences are not restricted to the toy
> scenario you gave.
I don't know what "toy scenario" are you refering to, but certainly
emacs -Q
M-: (make-frame '((visibility))) <RET>
is not a toy scenario *at all*. For one, it will prevent
frameset-restore to restore invisible frames (I could work around it,
but it'll be a hack).
> No. But we apparently have the problem that Emacs on Windows thinks
> that a frame is invisible although it isn't. And we have to find out
> where this notion of invisibility gets introduced - maybe it's easy to
> spot it, maybe, likely it's part of my pixelwise changes, and we can
> withdraw my "fix" soon.
I think bug#14841 is a clue that the visibility mismatch between Emacs
and the Windows wm predates your pixelwise changes.
> But till then we have to live with the
> situation that on Windows invisible Emacs frames are visible :-(
I would certainly prefer that you reverted your last change. You're
fixing an occasional problem and introducing a perfectly repeatable
one.
J
next prev parent reply other threads:[~2014-03-10 14:48 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 [this message]
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
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=CAAeL0STVxKir8gTaizHcfXAa-mUuoT0sJyJOxpbZM6q8MjyLyQ@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=16967@debbugs.gnu.org \
--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.