Re: menus (was Re: proposal for limiting menu icons color and size)
In article <[🔎] 19970311134122.43824@kite.ml.org> you write:
>Susan G. Kleinmann:
>> I'm one of the troglodytes that hasn't implemented menus in my packages yet.
>> I looked briefly at the information on the menu system that I could find,
>> and I couldn't figure out what the purpose of the menu system actually was.
>> As a user, I don't want anyone or any program "adjusting" my fvwm2 menus;
>> they were painful enough to set up in the first place (I find fvwm2 much
>> clumsier than fvwm in this respect.)
>
>This is exactly the point of the menu system. It's very painful to keep
>your fvwm menus in sync with what's actually installed on your system. The
>menus automate this.
[snip]
To be honest, I've found it fairly trivial to integrate the Debian menus
into an existing .fvwmrc. An m4 "include" in the right place and one extra
menu definition gives me a "Debian" submenu without affecting the rest of
my horribly-hacked fvwm setup.
[snip]
>Well sure. But menus are invaluable if you don't know what programs are
>installed on the system, especially for new users. There are a lot of
>commands that arn't typically used in pipes, such as mail programs, web
>browsers, games, editors, paint programs, etc. It's useful to have such
>programs on the menus.
Agreed, It really helps for the newbies, if nothing else...
--
Steve McIntyre, CURS Secretary, Cambridge, UK. stevem@chiark.greenend.org.uk
CUWoCS Honorary Vice-Chair-Thing Cthulhu - Why vote for the Lesser Evil?
<a href=http://hammer.chu.cam.ac.uk/~mdm1004/CUWoCS.html>CUWoCS home page</a>
"Tongue-tied & twisted, Just an earth-bound misfit, I..." |Finger for PGP key
Reply to: