[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#49959: 28.0.50; Emacs got quasi freeze
From: |
Masaru Nomiya |
Subject: |
bug#49959: 28.0.50; Emacs got quasi freeze |
Date: |
Mon, 23 Aug 2021 08:11:37 +0900 |
User-agent: |
Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM-LB/1.14.9 (Gojō) APEL-LB/10.8 EasyPG/1.0.0 Emacs/28.0.50 (x86_64-openSUSE-linux-gnu) MULE/6.0 (HANACHIRUSATO) |
Hello,
Sorry for late reply.
In the Message;
Subject : bug#49959: 28.0.50; Emacs got quasi freeze
Message-ID : <b0008bc4-4715-5313-2e10-5631092437a1@gmx.at>
Date & Time: Sun, 22 Aug 2021 18:54:11 +0200
[RM] == martin rudalics <rudalics@gmx.at> has written:
RM> [1 <text/plain; utf-8 (7bit)>]
RM> > Maybe the problem can be summarized as follows:
RM> >
RM> > - Emacs is in a state where a frame is hidden but not iconified.
RM> >
RM> > - Emacs gets a PropertyNotify event but does not react because the frame
RM> > was in its understanding _not_ iconified before. Elightenment thinks
RM> > that Emacs should understand that the frame is visible now and react
RM> > properly.
RM> >
RM> > If that's the case, then Emacs had this problem ever since. Actually,
RM> > Emacs here waits for a MapNotify event to arrive but apparently this
RM> > does not happen with Elightenment.
RM> A preliminary patch based on the above remarks is attached.
Thanks, but it's off the mark.
The issue is around rendering. The phnomenon is;
> If i move to another virtual desktop, and then return to
> the one with the emacs window, it looks like emacs never gets focus.
> Enlightenment's borders do change colours to indicate it has focus,
> but the cursor remains an empty box instead of a solid rectangle.
> Typing in the window also shows nothing happening. Until... If i
> minimize the window and bring it back, or if i shade and unshade the
> window, it all looks ok again, and everything i typed is there! So i
> can be typing blindly with nothing appearing in the window, then shade
> and unshade, and see that everything i typed (more often than not on
> the wrong line, because i couldn't see it).
Regards.
---
┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp
┃\/彡
┗━━┛ "No Windows, no gains!" ..... "Why, I am wrong?"
-- Bill --
- bug#49959: 28.0.50; Emacs got quasi freeze, 野宮 賢 / NOMIYA Masaru, 2021/08/09
- bug#49959: 28.0.50; Emacs got quasi freeze, martin rudalics, 2021/08/18
- bug#49959: 28.0.50; Emacs got quasi freeze, Masaru Nomiya, 2021/08/21
- Message not available
- bug#49959: 28.0.50; Emacs got quasi freeze, Masaru Nomiya, 2021/08/21
- bug#49959: 28.0.50; Emacs got quasi freeze, martin rudalics, 2021/08/22
- bug#49959: 28.0.50; Emacs got quasi freeze, martin rudalics, 2021/08/22
- bug#49959: 28.0.50; Emacs got quasi freeze, martin rudalics, 2021/08/22
- bug#49959: 28.0.50; Emacs got quasi freeze,
Masaru Nomiya <=
- bug#49959: 28.0.50; Emacs got quasi freeze, martin rudalics, 2021/08/23
- bug#49959: 28.0.50; Emacs got quasi freeze, Masaru Nomiya, 2021/08/23
- bug#49959: 28.0.50; Emacs got quasi freeze, Masaru Nomiya, 2021/08/23
- bug#49959: 28.0.50; Emacs got quasi freeze, martin rudalics, 2021/08/24
- bug#49959: 28.0.50; Emacs got quasi freeze, Masaru Nomiya, 2021/08/24
- bug#49959: 28.0.50; Emacs got quasi freeze, martin rudalics, 2021/08/24
- bug#49959: 28.0.50; Emacs got quasi freeze, Masaru Nomiya, 2021/08/25
- bug#49959: 28.0.50; Emacs got quasi freeze, martin rudalics, 2021/08/25
- bug#49959: 28.0.50; Emacs got quasi freeze, Masaru Nomiya, 2021/08/25
- bug#49959: 28.0.50; Emacs got quasi freeze, martin rudalics, 2021/08/26