Q: Debian, fvwm, virtual desktops and howto place specific programs at startup
Dear all,
I make use of fvwm on Debian unstable and start fvwm with startx. I
have seveal virtual desktops. On some, the first thing I do after
starting fvwm is placing the same programs every time, e.g. jpilot on
the first virtual desktop.
My question: Is there a way to specify for startup of fvwm where to
place which programs, i.e. can I automate the launching of jpilot on
the first virtual desktop?
Thanks for any enlightment,
Lukas
--
Lukas Ruf
http://www.lpr.ch http://www.maremma.ch
http://www.{{topsy,nodeos}.net,{promethos,netbeast,rawip}.org}
Wanna know anything about raw ip? Join [EMAIL PROTECTED] on www.rawip.org
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Q: Debian, fvwm, virtual desktops and howto place specific programs at startup
-- Lukas Ruf [EMAIL PROTECTED] wrote (on Tuesday, 29 October 2002, 04:51 PM +0100): I make use of fvwm on Debian unstable and start fvwm with startx. I have seveal virtual desktops. On some, the first thing I do after starting fvwm is placing the same programs every time, e.g. jpilot on the first virtual desktop. My question: Is there a way to specify for startup of fvwm where to place which programs, i.e. can I automate the launching of jpilot on the first virtual desktop? Use .xinitrc to start programs on startx. In terms of getting them to place in specific areas, if the program has a --geometry option, this would be the way to go. As an example, #!/bin/sh # Start up some important servers... numlockx xscreensaver -no-splash exec fvwm Make sure that the last line executes your window manager, and that you precede it with exec; also, be sure that any programs preceding this line are executed in the background (e.g., are followed by the operator). In blackbox, there's two tools, bblaunch and bbappconf, that can configure which workspace (note: *not* virtual desktop) a program starts on. A patch for bbappconf, located at http://xor.orodu.netbb/bbappconf.move_resize_fix_iconify.patch also allows you to specify geometry for an application that doesn't have a --geometry option. I *don't know* if either of these tools work with other window managers. They might be worth looking into, however. -- Matthew Weier O'Phinney [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Q: Debian, fvwm, virtual desktops and howto place specific programs at startup
On Tuesday 29 October 2002 08:39, Matthew Weier O'Phinney wrote: In blackbox, there's two tools, bblaunch and bbappconf, that can configure which workspace (note: *not* virtual desktop) a program starts on. A patch for bbappconf, located at http://xor.orodu.netbb/bbappconf.move_resize_fix_iconify.patch also allows you to specify geometry for an application that doesn't have a --geometry option. I *don't know* if either of these tools work with other window managers. They might be worth looking into, however. no, they don't. They are currently written only for blackbox. They will be ported to netwm/ewmh soon. However, last I checked fvwm did not support ewmh yet and instead still used its own protocol. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Q: Debian, fvwm, virtual desktops and howto place specific programs at startup
On Tuesday 29 October 2002 16:51, Lukas Ruf wrote: Dear all, I make use of fvwm on Debian unstable and start fvwm with startx. I have seveal virtual desktops. On some, the first thing I do after starting fvwm is placing the same programs every time, e.g. jpilot on the first virtual desktop. My question: Is there a way to specify for startup of fvwm where to place which programs, i.e. can I automate the launching of jpilot on the first virtual desktop? Yes, fvwm is highly configurable. If you have something like Style jpilotStartsOnPage 1 0 in your ~/.fvwm2rc, then anytime and no matter how you start Jpilot, it will be put in the appropriate Page. Also, if you have something like AddToFunc InitFunctionI Exec jpilot jpilot will be started automatically when fvwm starts. Note however, that this applies to fvwm2, which is now called fvwm. The old fvwm is now called fvwm1 and afaik cannot do this. Thanks for any enlightment, Lukas You're welcome, Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
