On Wed, 17 Apr 1996, David SEGONDS wrote:
> Hello,
>
> I currently have a problem due to an interaction between
> Xemacs 19-13 and fvwm-2.0.42. If I iconify and then de-iconify an
> Xemacs frame, the frame in question becomes unusable: I can't type in
> it but I can still open a new frame.
>
> I've read something about this in BUGS. Is it a bug from fvwm2
> or from xemacs 19.13? Is there a solution to go around this problem
> except by avoiding the iconification?
>
I have the same behavior with xemacs 19.13 and fvwm2 2.0.42, except
it happens when I restart. And it doesn't happen every time.
When it happened the last time, iconify and de-iconify worked and went
back everything normal.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Toshi Isogai $_at_0k3-MxL@(J
-- I am an ASIC engineer, not a sick engineer --
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Wed Apr 17 1996 - 11:38:23 BST