palto42 I also use the binary package since both the Snap as well as the open source version from the Solus repository have some restrictions (small or big depends on your use case...).
amirhosseinak20 palto42 HI, thanks for your script. how can i start vscode binaries from terminal, should i make an alias for it or ... .
gnomo223 Me too kkkk. I only have one question, i need to create a "file.sh" and introduce your sript via nano ?
palto42 gnomo223 Below the script you can right-click on the view raw and then "Save target as.." (simpler than copy & paste to nano). Same for the .desktop files which you need to save in ~/.local/share/applications/ .
palto42 amirhosseinak20 From terminal you can start VScode with /home/user/bin/VSCode-linux-x64/code --no-sandbox (replace the path with your installation folder). I have a symlink in my /home/user/bin folder and this folde in the PATH, but you can also add an alias.
over-core palto42 Hi, these scripts is what I was looking for. Snaps do not work reliably and OSS version of VSCode can't access remote dev servers via ssh due to some license limitations. Proprietary binaries can do it, but there's hassle with updating.
palto42 One of the issues with current Snap packages is the restrictions it has on file system access, see discussion on launchpad: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1643706, which makes it essentially unusable for some use cases.
