Package Details: visual-studio-code 1.19.0-3

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: 525
Popularity: 39.983195
First Submitted: 2015-04-29 17:53
Last Updated: 2017-12-15 10:09

Pinned Comments

dcelasun commented on 2017-11-15 06:20

FREQUENTLY ASKED QUESTIONS (read before flagging or commenting!)

- There is a new version out, why is the package not updated?

Please check this page [0] before flagging as out-of-date. If there is no new version on that page, it's not yet released. A tag on Github is NOT a release! If you can see the new version on the updates page but the AUR package is still not updated, flag it and give it time. It's usually done within a day or two.

- Why is $X a dependency? I don't like it.

Just because $X is not required to open the app, doesn't mean there is nothing that depends on it. Always search the comment history [1] on AUR to see if that dependency has been previously discussed before writing your own comment. Still nothing? Then use namcap [2] to make sure it's _really_ not needed. If namcap doesn't complain, please leave a comment here and I'll investigate.

- Something is broken with the app, where do I report it?

The problem might be a packaging issue (wrong paths, dependencies, icons etc), so please write a comment here first. If you don't get a reply, or if someone says it's an upstream issue, you can report it on Github [3].

- This is a binary package, why does it not have a -bin suffix? I want you to change it.

It's like that for historical reasons and no, it won't be changed. Read the comment history [1] for details.

- I have a problem with the package or the program itself, can I email you?

No. You won't get a reply. Leave a comment here instead and be patient.


Latest Comments

dcelasun commented on 2017-12-15 10:10

OK, just pushed another release. Now /usr/bin/code is a symlink to the shell script, but the .desktop file calls the binary. Seems to be working as expected for me.

SneakySnake commented on 2017-12-15 08:21

Would it be possible for code to be a wrapper script that calls the CLI script if we are in a tty, and the binary otherwise?

I'm asking because if we launch the binary from a terminal, it gives the ioctl error message described below, and the process doesn't get detached from the terminal. Not a big deal, but still annoying.

elgs commented on 2017-12-15 07:56

bash: cannot set terminal process group (-1): Inappropriate ioctl for device bash: no job control in this shell

When I upgraded to the following version, I got the error message above each time I start code:

Version 1.19.0 Commit 816be6780ca8bd0ab80314e11478c48c70d09383 Date 2017-12-14T09:56:48.842Z Shell 1.7.9 Renderer 58.0.3029.110 Node 7.9.0 Architecture x64

dcelasun commented on 2017-12-15 07:06

@aguniyal: It's a packaging issue and it's fixed now. Next time, please read the pinned comment before opening an issue upstream.

agauniyal commented on 2017-12-15 06:49

Opening via dmenu has different behaviour now -

dcelasun commented on 2017-12-11 20:25

@teej: I think you have a corrupted file.

$ sha256sum visual-studio-code.desktop

de88d95db3f55ce58ffd3c229cbde566099384d4f005cf887b00ccaeed605984  visual-studio-code.desktop

teej commented on 2017-12-11 20:13

The latest version has an invalid checksum for the .desktop file. I was able to install it by manually changing the checksum.

Alko89 commented on 2017-11-24 21:57

yup, its OK now...strange, I tried downloading the file three times with the same result

Marcel_K commented on 2017-11-24 21:11

Probably a network error. Just run makepkg again.

Alko89 commented on 2017-11-24 21:04

Does anyone have issues with the latest snapshot? Mine has the site of 0 bytes and tar gives mi an error `tar: This does not look like a tar archive`

All comments