Hello all - I'm looking for some advice to solving a minor annoyance
between xemacs and fvwm2. This might be a xemacs problem, but I thought
I'd try here first.
I'm running fvwm2 (see below for exact version) with multiple desktops.
I run xemacs with gnuserve, and I then use gnuclient from a fvwm2
menu to spawn new xemacs frames. What I would like is the new xemacs
frame I create to always appear on the current desktop. What happens
though is that the created frame always appears on a desktop with an
existing xemacs frame instead of the current desktop.
This doesn't appear to be a StartsOnDesk problem because (1) if I have
no current xemacs frames and I create one it appears on the current
desktop, (2) if I have one xemacs frame on desktop N, a new frame will
always appear on desktop N, no matter what N is. If I have multiple
xemacs frames already created on multiple desktops, a new frame will
always appear on one of those desktops - I haven't quite figured out
the logic as to where, but it seems to be consistantly with a certain
existing frame until I destroy it, then it shifts to another frame.
I have no StartsOnDesk for xemacs in my .fvwmrc2.
The only similar bug I found in the list archives was that xemacs 21.1.7
created new frames with the name 'shell' initially and that caused
StartsonDesk to map it unexpectedly. But that bug appears to be fixed in
21.1.8 (which is what I'm running).
So, anyone have any advice?
Thanks,
Von
p.s. - I'm running:
[FVWM][main]: Fvwm Version 2.2 compiled on Apr 9 1999 at 16:15:38
XEmacs 21.1 (patch 8) "Bryce Canyon" [Lucid] (i686-pc-linux) of Tue Feb 1 2000 on cerberos2.ncsa.uiuc.edu
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Wed Feb 09 2000 - 15:44:29 GMT