Re: fvwm2 menus burned

1997-04-23 Thread Neil A. Rubin
What you say about Afterstep is no longer accurate, as of 0.99pre6-1 (upstream 1.0pre6) since I have changed things so that the Debian Afterstep now has m4 support compiled in so that we can now use m4 includes for the Debian menus. This is much better than the old method of using a skeleton file

Re: fvwm2 menus burned

1997-04-22 Thread Rick Jones
If I remember correctly the /etc/menus dir is for pkgs you want skipped when update-menus is run. Maybe skipped is incorrect. It's not updated by the program but the super-user. Meaning that nothing added by dpkg will be added to the menus in this dir. Making the menu system non-operational if

Re: fvwm2 menus burned

1997-04-20 Thread Karl M. Hegbloom
> "Dima" == Dima <[EMAIL PROTECTED]> writes: Dima> In message <[EMAIL PROTECTED]> Dima> you wrote: >> But now something keeps adding a DestroyMenu MainMenu to the >> "/etc/X11/fvwm2/menudefs.hook" file, so my premainmenu.hook >> stuff gets wiped out by it. It started

Re: fvwm2 menus burned

1997-04-19 Thread Richard Morin
On Sat, 19 Apr 1997, joost witteveen wrote: > If you've got the menu package installed, the /etc/x11/fvwm2/menudefs.hook > file is auto-generated by "update-menus", and thus should not be > edited. If you want to add menuentries, you can > -add them to the end of the menu in your /etc/X11/fvwm2

Re: fvwm2 menus burned

1997-04-19 Thread Dima
In message <[EMAIL PROTECTED]> you wrote: ... > But now something keeps adding a DestroyMenu MainMenu to >the "/etc/X11/fvwm2/menudefs.hook" file, so my premainmenu.hook stuff >gets wiped out by it. It started after the last upgrade, to the BETA >version. I have `bug` reported it. That's one o

Re: fvwm2 menus burned

1997-04-19 Thread joost witteveen
> Dima writes: > > > > I dunno about changing stuff on reboot, but the easiest way to fix > > fvwm2 is to put your customizations in ~/.fvwm2/*.hook files. > > > > You'll probably need to experiment a little to get it right -- I did, > > but if you get stuck I can send you my config file

Re: fvwm2 menus burned

1997-04-19 Thread Karl M. Hegbloom
Dima writes: > > I dunno about changing stuff on reboot, but the easiest way to fix > fvwm2 is to put your customizations in ~/.fvwm2/*.hook files. > > You'll probably need to experiment a little to get it right -- I did, > but if you get stuck I can send you my config files. I did tha