[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: X, new problems.
>
> Donovan Rebbechi wrote:
> >
> > On Tue, 9 Feb 1999, Kevin Forge wrote:
> >
> > > Donovan Rebbechi wrote:
> > > >
> > > > it would be simple enough to write a two line hack perl script that
> > > > fixes the config file ( just remove all "Virtual" lines ).
> > >
> > > Speaking of "simple" scripts... How about an extension of
> > > KAppfinder that would basically make the whole FVWM2 menu into
> > > a sub menu on the 'K' menu ?
> >
> > I believe wmconfig already does this ... and the way it works is somewhat
> > nicer than kappfinder. You just need to run wmconfig --output=kde before
> > starting kde ( you can put it in the startkde script or in .xinitrc )
> > My startkde script ( which was included in my kde build sometime back )
> > ran wmconfig. ( I think ) this has been incorporated into our subsequent
> > kde packages.
> >
> > The problem OTOH of just putting the entire fvwm menu on the Kmenu is
> > that its not dynamic. Better to just put the wmconfig output there IMO.
> >
The "wmconfig --output=kde" command is automatically run in Indy when
KDE is started. This allows us to have the whole set of command menus
available from KDE even for those commands who are not in kappfinder.
--
Jean Francois Martinez
Project Independence: Linux for the Masses
http://www.independence.seul.org