I think you are wrong because is not designed to
change menu layout but to add own submenu(s), it's why it should be
after common menu definitions but is it before any menu-specific layout
items or after them is irrelevant, and if it placed before that makes
menu editing more simple as it will not
calling this invalid due to not meeting the specifications.
** Changed in: lxlauncher (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1191530
Title:
Menu conf
read above message from the developer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1191530
Title:
Menu config file merge menus from standard locations too soon so
defaults override merges.
To m
this is certainly outside of the understanding of the upstream
developer. if you wish to convince him, i would recommend filing a bug
report there, since this is really not an ubuntu issue, but an lxde one.
still, it is outside the scope as the developer sees it, so you'd have
to convince him:
htt
On Tue, 4 Nov 2014, Walter Lapchynski wrote:
> calling this invalid due to not meeting the specifications.
Which specification are you looking at? Any setting in
/etc/xdg/menus/applications-merged, ~/.config/menus should be able to
override the system menu config.
http://standards.freedesktop.
On Tue, 4 Nov 2014, Walter Lapchynski wrote:
> read above message from the developer.
I did, I dissagree, see my post above (which refers to the same documents
he does BTW), I give up. Again KDE does get this right.
xfce, gnome (when it still had a working menu) and lxde do work correctly
when
