Test: running vscode with gksudo or sudo permission

[Tyriar]

• @aeschli

Test plan for #3068

• Test Ubuntu
• Test Fedora

Basic test case

sudo mkdir ~/perms-test
sudo touch ~/perms-test/file
sudo code-alpha --user-data-dir ~/root-data-dir ~/perms-test
# edit and save `file` in vscode

Known limitations

• Files can only be saved if the root user has write access, you can check file permissions using ls -la. Example output gives -rw-r--r-- which means user read/write, group read, all read. If the 'daniel' user owns this file, 'root' will be able to read but not save.
• Opening the browser via vscode will hang the editor, see Calls to shell.openExternal hang vscode when running as root user #5063

[aeschli]

Running sudo code-alpha --user-data-dir ~/root-data-dir ~/perms-test results in

It is recommended to start vscode as a normal user. To run as root, you must specify an alternate user data directory with the --user-data-dir argument.

sudo code-alpha --user-data-dir=~/root-data-dir ~/perms-test, however, works.

[Kowus]

I use Ubuntu 14.04.5 x86 and "code-alpha" isn't a recognized command. However, when I run

sudo code --user-data-dir=~/root-data-dir ~/perms-test, it worked