Package Details: visual-studio-code 1.15.1-2

Git Clone URL: (read-only)
Package Base: visual-studio-code
Description: Visual Studio Code: Editor for building and debugging modern web and cloud applications (official binary version)
Upstream URL:
Keywords: code studio visual visual-studio-code vscode
Licenses: custom: commercial
Provides: vscode,visualstudiocode
Submitter: dcelasun
Maintainer: dcelasun
Last Packager: dcelasun
Votes: 444
Popularity: 40.382071
First Submitted: 2015-04-29 17:53
Last Updated: 2017-08-17 15:48

Latest Comments

aurgrans commented on 2017-08-17 18:56

I did some research about the ALT+TAB problem which is actually caused by vscode (that's why there's no Gnome bug report about it)

I think vscode doesn't register correctly with X11, where Gnome (the default ALT+TAB, not Alternatetab) gets the list of windows.
That's probably why it works fine using another desktop environment (tested it on KDE and, to check if it's an Arch Linux only problem, Ubuntu 1704's Unity) or using Gnome in wayland mode.

So in my opinion, the best solution for Gnome-X11 users is to use the preinstalled extension Alternatetab and for other desktop environment or Gnome-wayland it should work anyway. To make it work on Gnome-X11 without Alternatetab you can just hope for a vscode update

dcelasun commented on 2017-08-17 15:49

All right, I've readded StartupWMClass since there is now a workaround for Gnome (thanks @aurgrans).

I couldn't find an upstream Gnome bug report about this, but if anyone finds one or files it, please post it here as well.

TamasBarta commented on 2017-08-17 15:35

When I add StartupWMClass=code, nothing breaks on KDE. It is not a problem with the desktop file, but with the DE, I believe.

aurgrans commented on 2017-08-17 15:28

I think I figured out why I don't have the issue not seeing vscode in ALT+TAB.

Have a look at the Gnome extension Alternatetab (which is installed by default if I remember right)

With it enabled and StartupWMClass=Code everything works fine for me

I hope this hint helps solving those problems!

dcelasun commented on 2017-08-17 05:13

@aurgrans: Please read the several comments below yours. Adding StartupWMClass causes a different (and I think worse) problem.

aurgrans commented on 2017-08-17 02:11

Please add StartupWMClass=Code to the .desktop file. Without this line Gnome's Dash to Dock doesn't recognize the window to be vscode. (with StartupWMClass=Code) (without it)

dcelasun commented on 2017-08-16 08:59

No, this package uses the official upstream distribution without any modifications. Someone already asked this in the -oss package [0], I recommend waiting for an answer there.


TamasBarta commented on 2017-08-16 08:56

Any chance to make this use the "electron" package? I don't know what it takes unfortunately.

dcelasun commented on 2017-08-11 22:25

I've tried it [0][1] with the upstream stuff, including renaming things to "code" instead of "visual-studio-code"; it doesn't work. Adding StartupWMClass=code (or Code) makes the icon invisible in alt+tab, removing it causes the app to use a different icon.

I'll investigate more, but if anyone has an idea, it'd be appreciated.


xaver commented on 2017-08-11 21:23

The second icon issue was exactly why it was added in the upstream .desktop file:
Maybe, it would be best to just ship with the upstream file:
This would btw also enable the "New Window" feature in Gnome Shell etc.

All comments