On Wed, Oct 13, 1999 at 02:17:46AM -0600, kibble_at_guyver.dhs.org wrote:
>
>
> On Wed, 13 Oct 1999, Shao Zhang wrote:
>
> > Hi,
> > I don't have the Delete key binded. So I just quickly changed
> > the fvwmrc file to have F11 to do that. And Both Delete and
> > Destory killed the children.
> >
> > Shao.
> >
> > Dominik Vogt [dominik.vogt_at_fvwm.org] wrote:
> > > On Wed, Oct 13, 1999 at 05:02:34PM +1000, shao_at_cia.com.au wrote:
> > > > Dominik Vogt [dominik.vogt_at_fvwm.org] wrote:
> > > > > On Wed, Oct 13, 1999 at 02:34:47PM +1000, shao_at_cia.com.au wrote:
> > > > > > Hi,
> > > > > > Thanks for the reply.
> > > > > >
> > > > > > I fork them to background immediately after start up.
> > > > > >
> > > > > > shao:/home/shao$ licq &
> > > > > > [1] 8950
> > > > > >
> > > > > > But typing exit in xterm won't kill licq. I will try your
> > > > > > suggestions.
> > > > >
>
> Well hardly being the expert here but all the window managers that I've
> tried also do this. Those including Window Maker, AfterStep, E, TWM,
> Olvwm and a few others hardly worth mentioning. I just use the start from
> xterm and exit the xterm which seems to work just fine for me.
Well, it's not a problem of the window manager at all. Although I may
not have stated this in my previous mails. The reason why I still try
to find out what's going on is:
1) Shao mentioned the licq is the only app. with this problem
(although that doesn't say much). And he said it doesn't happen
with fvwm version 1.x
2) I'm and old shell freak and always willing to learn.
Bye
Dominik ^_^
--
Dominik Vogt, Hewlett-Packard GmbH, Dept. BVS
Herrenberger Str.130, 71034 Boeblingen, Germany
phone: 07031/14-4596, fax: 07031/14-3883, dominik_vogt_at_hp.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 Wed Oct 13 1999 - 05:43:14 BST