Your message dated Sat, 23 Feb 2008 08:47:07 -0600
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#467130: FVWM should not read
/etc/X11/fvwm/menudefs.hook by default
has caused the Debian Bug report #467130,
regarding FVWM should not read /etc/X11/fvwm/menudefs.hook by default
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
467130: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=467130
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: fvwm
Version: 2.5.24-1
On startup fvwm reads the file /etc/X11/fvwm/menudefs.hook by default before
reading any user config files.
This file should not be read by default and the user should have the option to
read it or not in their own config file via the 'Read
/etc/X11/fvwm/menudefs.hook' command.
Reason is fvwm as an extreammly configureable windowmanager should leave the
ability to add menus in the option of the user and not put a large menu such as
the /DebianMenu in by default.
jaimos
--- End Message ---
--- Begin Message ---
Hi,
On Sat, 23 Feb 2008 02:13:08 -0700, Jaimos Skriletz
<[EMAIL PROTECTED]> said:
> On startup fvwm reads the file /etc/X11/fvwm/menudefs.hook by default
> before reading any user config files.
This is done to set up the default actions, in case the user
does not have a configuration file. This way, even for an unconfigured
setup, the standard Debian menu is supported. The menu package is part
of policy, and this requirement is imposed there.
> This file should not be read by default and the user should have the
> option to read it or not in their own config file via the 'Read
> /etc/X11/fvwm/menudefs.hook' command.
You can elect to read it in your .config, or ignore it.
> Reason is fvwm as an extreammly configureable windowmanager should
> leave the ability to add menus in the option of the user and not put a
> large menu such as the /DebianMenu in by default.
This has no real practical impact on a user. You can just not
bind /DebianMenu to any key, and it is invisible. You can bind it into
a menu of your choosing -- or you can ignore /DebianMenu and bind the
submenus into your own top level menus, which is what I do.
This is not a bug. This does not restrict the flexibility of
fvwm in any significant manner, and allows fvwm to conform to Debian
policy.
manoj
--
Violence is molding.
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.golden-gryphon.com/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--- End Message ---
