woof-CE
woof-CE copied to clipboard
puppylinux-woof-CE
The VS Code menu entry doesn't work
#2909 makes code (/usr/bin/code) work.
But the menu entry is broken, because it runs a different executable and /usr/bin/code is not a symlink to it.
#2909 makes
code(/usr/bin/code) work.But the menu entry is broken, because it runs a different executable and /usr/bin/code is not a symlink to it.
what about instead run-as-spot, just add --no-sandbox parameter in order to run it as root?
what about instead run-as-spot, just add --no-sandbox parameter in order to run it as root?
Running it as root is a bad idea in first place, especially with --no-sandbox. Some development tools want to run as a regular user, so the terminal inside the IDE becomes unusable and you must Alt-Tab frequently to get any work done.
Maybe it should also account for the second executable and run-as-spot that too?
The question is, how to find the second executable. fixmenusd monitors newly created executables under /usr/bin, and newly created .desktop files under /usr/share/applications. But it doesn't parse the .desktop files, and I'm not sure if I want to do this.
If we know that they are related (you could examine via htop for example, then search all the .desktop files for a matching text line) we could monitor for that specific case. Via wildcards, etc.