On Fri, Feb 11, 2000 at 09:21:09AM -0600, vwelch_at_ncsa.uiuc.edu wrote:
> On Thu, Feb 10, 2000 at 05:45:17AM +0100, Dominik Vogt wrote:
> > On Wed, Feb 09, 2000 at 03:44:15PM -0600, Von Welch wrote:
> > > 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?
> >
> > You could set up FvwmEvent to move newly created Xemacs windows
> > to the current desk. I don't have the correct syntax handy
> > right now, but let FvwmEvent execute something like
> >
> > Current (emacs*) movetodesk ...
> >
> > when new windows are mapped.
>
> I don't believe this will actually work without hacking FvwmEvent.
> As far as I can tell, by both experimentation and looking at the
> source, *FvwmEvent and *FvwmEvent both only take a single whitespace
> delimited token for command and action, so the most you can have is
> two words in any given command.
>
> In other words, with the following everything after "Current" is
> discarded by FvwmEvent:
>
> *FvwmEvent add_window Current (emacs*) MoveToDesk 0
>
> I don't believe it would be difficult to modify FvwmEvent.c so
> that it uses the whole string instead of just the next token,
> however I also have the problem that the xemacs frames don't receive
> focus automatically. I understand the 2.3.x fvwm2 has GrabFocus, but
> I haven't found any way in 2.2.x to achieve this yet.
You can make the XEmacs windows 'ClickToFocus'. Then they will
receive focus as soon as they are mapped.
Bye
Dominik ^_^
--
Dominik Vogt, Agilent Technologies, Dept. BVS
Herrenberger Str.130, 71034 Boeblingen, Germany
phone: 07031/464-4596, fax: 07031/464-3883, dominik_vogt_at_agilent.com
--
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 Fri Feb 11 2000 - 10:22:40 GMT