Re: Fvwm.... this actually didn't work........
On Mon, Oct 6, 2014 at 12:37 PM, Charlie <ariestao@ipstarmail.com.au> wrote:
>
> This actually didn't work in my ~/.fvwm/functions directory:
>
> #----------------------------------------------------------------------------
> # This is the Debian menu call as suggested by Vincent W Chen.
> # Debian Menu
> #----------------------------------------------------------------------------
>
> DestroyFunc SetDebianMenu
> AddToFunc SetDebianMenu
> + I Read /etc/X11/fvwm/menudefs.hook
> + I Read ~/.fvwm/menudefs.hook
> Test (f /etc/X11/fvwm/menudefs.hook) SetDebianMenu
>
> The /etc/X11/fvwm/menudefs.hook was overwritten when I updated/upgraded
> this system today and I had to add Kate in editors manually in that
> file.
>
This is expected.
> The update and upgrade didn't touch my ~/.fvwm/menudefs.hook
>
This is also expected.
I think you are missing the whole point of the Debian menu. Let's
start from the beginning. There are thousands of programs in the
Debian repository that you are free to install. There are word
processors, web browsers, audio players, editors (e.g. Kate), and many
more. There are also multiple window managers in the repository, Fvwm
being one of them. Many window managers provide menus for users to
open programs with, and Fvwm is no exception.
Now, what happens when you install/uninstall a program? Normally,
you'd have to edit your menu so that the entry corresponding to the
installed/uninstalled program is inserted/deleted. Keeping all the
available program on your system in sync with the menu is a lot of
work, so developers came up with the Debian menu. The Debian menu
automatically generates the list of program on your system, so you no
longer have to keep track of what you have installed/uninstalled. Fvwm
is able to make use of the output from the Debian menu, and --- here's
the key --- the final output is stored in /etc/X11/fvwm/menudefs.hook.
This means that:
- Every time a new menu is generated (automatically on program
install/uninstall, or manually), /etc/X11/fvwm/menudefs.hook is
modified. That's why I suggested you leave the file alone.
- Nothing will ever touch the stuff in your home directory, including
~/.fvwm/menudefs.hook.
> Should I delete the + I Read /etc/X11/fvwm/menudefs.hook out of that
> entry above to make it just read the file I want?
>
> Should I change tis line:
> Test (f /etc/X11/fvwm/menudefs.hook) SetDebianMenu
> to
> Test (f /home/charlie/.fvwm/menudefs.hook) SetDebianMenu
> ?????
>
Depends on what you want to do:
- If you want to have the automatically generated menu (the whole
point of Debian menu, so you don't have to manually maintain your own
menu), then keep the /etc/X11/fvwm/menudefs.hook.
- If you copied the /etc/X11/fvwm/menudefs.hook to
~/.fvwm/menudefs.hook, then there's no need for the
/etc/X11/fvwm/menudefs.hook entry. But then this defeats the whole
purpose of the Debian menu, since you now have to maintain your own
~/.fvwm/menudefs.hook.
> If no one knows I will have to experiment.
>
> Maybe remove /etc/X11/fvwm/menudefs.hook from the system altogether, so
> many things to try, so many combinations?
>
The file is part of the Fvwm package, so it might be recreated when
Fvwm is upgraded.
> I have to enter a couple of other packages manually, like scribus,
> okular etc., as an example? Reading the Debian menu and updating the
> Debian menu never added these. I always felt even before when I used
> it, that fvwm was against anything KDE.
>
This has nothing to do with Fvwm. Again, Fvwm only provides the menu
from the Debian 'menu' package. It does not change the output in any
way. Whether there is a menu entry for a particular package depends on
whether the package (scribus, ocular, what have you) provides a menu
entry. There is nothing the Fvwm package can do on that front.
Note that though the Fvwm _package_ can't do anything, you are of
course free to add the menu entry yourself.
> Anyway, I don't mind adding these manually as long as I can make fvwm
> read only my ~/.fvwm/menudefs.hook and not the other one.
>
If you want to maintain your own menu, then there's no need for any
lines involving /etc/X11/fvwm/menudefs.hook. Replace all such lines
with ~/.fvwm/menudefs.hook.
Regards,
Vincent
Reply to: