Open brianjmurrell opened 3 years ago
This is how MenuLibre works today. When you edit a system-installed launcher, it creates a copy in ~/.local/share/applications/
. When you delete your new user-installed launcher, it is replaced by the system one.
Are you seeing something different on your end?
When you delete your new user-installed launcher
Well, this is the issue. How is it deleted exactly? Do you mean I open a bash shell and use an rm
command?
That said, quite honestly, I opened this issue so long ago, my recollection of exactly what the problem was is very fuzzy. Futzing with menu items in GNOME is something I do maybe once a year and this issue would just have been something I found the last time I did any menu item futzing and as you can see that was almost a year ago.
It would be nice/interesting to have an option to revert a local .desktop item and fall back to the system supplied one, where that's possible.
Imagine for example I add a command-line argument to
/usr/share/applications/org.gnome.Evolution.desktop
which would create a~/.local/share/applications/org.gnome.Evolution.desktop
.There should be an option to revert that back, effectively deleting
~/.local/share/applications/org.gnome.Evolution.desktop
but without removing the item from the menu structure.I see a couple of ways of achieving this. The more difficult way, by comparing the change being made with the system installed item and if the change is to effect making the local one the same as the system one (i.e. removing a previously added argument), instead of just removing the argument from the local .desktop entry, simply remove it.
A second way would be to have an option on the Delete button that asks if you really want to delete the menu item or just revert any local changes.
A third way is a dedicated "Undo" or "Revert" or "Reset" button which simply removes the local .desktop item.