Again, the Categories=<>; key is not what decides what apps go where,
according to the menu-spec.
Alacarte writes to ~/.config/menus/applications.menu or similar, which
should describe any user-configured overrides to the menus. If XFCE's
menu implementation does not support this format, then it i
The "Categories" field is only one way that the menu specification
decide what subfolder of the menu it will end up with. The menu spec
says that ~/.config/menus/applications.menu is what decides where menus
go.
Alacarte is a menu spec compliant editor. If XFCE does not respect the
menu spec, it's
>From the menu specification:
"Hidden should have been called Deleted. It means the user deleted (at
his level) something that was present (at an upper level, e.g. in the
system dirs). It's strictly equivalent to the .desktop file not existing
at all, as far as that user is concerned. This can als
The menu specification, which Unity follows, existed since long before
Unity was in the planning stages. Furthermore, the "Main Menu" application
used to edit menus is currently maintained by me, and I am not a Canonical
employee. They do not pay me any money, and I have no power over
Canonical's c
Pushed a more comprehensive fix to git master. Thanks! Not sure what
flags I'm supposed to set in Launchpad.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to alacarte in Ubuntu.
https://bugs.launchpad.net/bugs/1057600
Title:
alacarte
As the upstream maintainer of alacarte, if you have any of these
crashes, I'd love to see them. I do not know of
The editing bug may be caused not respecting $XDG_MENU_PREFIX.
http://git.gnome.org/browse/alacarte/commit/?id=a4db6799f41947b5cd08231e77d41c561d94170a
This commit should fix it. Plea
