This is primarily directed at those users who use fvwm-2.0.43 and a
recent version of XEmacs -- 19.14 or the latest 19.15 beta release.
Right now, I'm mainly interested in determining if anyone else can
verify this (or similar) lossage on another machine using fvwm-2.0.43
and XEmacs-19.1[45] and Gnus-5.
>> On 23 Dec 1996 10:36:38 -0800,
>> Steven L Baur(sb) wrote:
>>>>>> "mb" == Mark Borges <mdb_at_cdc.noaa.gov> writes:
mb> One other note -- I have set:
mb> focus-follows-mouse's value is t
mb> but it doesn't appear to solve anything for me.
Actually, it does help some (see below).
sb> It solves all the focus related stuff I've complained about in the
sb> past with olvwm.
So perhaps I'm witnessing an fvwm-2.0.43 bug...
mb> In particular, I was hoping this would correct the problem where
mb> the XEmacs display goes blank and does not return unless an
mb> iconify/de-iconify sequence is given. This happens consistently
mb> using fvwm-2.0.43 under the following scenario:
mb> (1) Start Gnus from the toolbar
mb> (2) Go to another desktop
mb> (3) Come back to the page containing the XEmacs Gnus
mb> frame. It's now blank.
sb> I've never noticed anything along those lines. You have reached the
sb> *Groups*/*Topics* buffer display, right?
In the above scenario, no. But if I let Gnus get to the point where it
shows it's splash screen (with the yellowish Gnu animal), and then
switch desktops, I'm OK.
sb> I've seen the display blank out while Gnus is initializing (or there
sb> is a long sequence of lisp code), but it always redisplays when I
sb> return to the desktop in question and XEmacs is idling in the command
sb> loop. This is possibly a fvwm bug? Do you have another virtual
sb> window manager to try your XEmacs settings with?
Yes. If I switch desktops in fvwm while the window is blank, I come
back to a blank window. But if I wait for the splash screen, as
described above, switch desktops and then come back I see the *Group*
buffer displayed. I don't believe this semi-win happens in
19.14. Perhaps the rest of the problem is in fact a bug in the fvwm
window manager. I'll try to grab olvwm and build it later to test this
out.
--
-mb-
--
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 Fri Dec 27 1996 - 11:11:49 GMT