Package Details: visual-studio-code-bin 1.45.1-1

Git Clone URL: (read-only, click to copy)
Package Base: visual-studio-code-bin
Description: Visual Studio Code (vscode): Editor for building and debugging modern web and cloud applications (official binary version)
Upstream URL:
Licenses: custom: commercial
Conflicts: code
Provides: code
Submitter: dcelasun
Maintainer: dcelasun
Last Packager: dcelasun
Votes: 897
Popularity: 13.30
First Submitted: 2017-12-18 19:14
Last Updated: 2020-05-14 19:41

Pinned Comments

dcelasun commented on 2017-11-15 06:20

FREQUENTLY ASKED QUESTIONS (read before flagging or commenting!)

  • What is the difference between this package and the one in the community repo?

This is the official binary distribution from Microsoft. The one in the community repo is an unofficial build made from source. Beyond the license difference and branding, there are some proprietary features not available in the open source version.

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

Please check this page 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.

  • I'm using an AUR helper (yay, yaourt etc.) and I can't install it. Why?

Sometimes AUR helpers do weird things. Download the tarball and install it manually with makepkg -si. If that works, report the problem to your AUR helper's upstream, not here.

  • When I install this package xdg-open uses vscode, not my file manager! How do I fix this?

Install shared-mime-info-gnome. Also see this reddit thread.

  • 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 on AUR to see if that dependency has been previously discussed before writing your own comment. Still nothing? Then use namcap 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), 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.

  • I have a problem with this package, can I email you?

No, you won't get a reply. Please stop doing this. Leave a comment here instead and be patient.

Latest Comments

1 2 3 4 5 6 ... Next › Last »

lordflaron commented on 2020-05-26 03:41

@emke Thanks, can confirm that it failed on pamac, but works with yay

emke commented on 2020-05-20 20:27

@lordflaron after the latest pamac update, I no longer get that error.

dcelasun commented on 2020-05-14 07:25

@lordflaron then that's a problem with pamac. Please read the pinned Frequently Asked Questions.

lordflaron commented on 2020-05-14 07:07

@dcelasun I'm using the pamac GUI with air support

dcelasun commented on 2020-05-14 06:24

@lordflaron that file is definitely in the package. How are you installing this package, with an AUR helper?

lordflaron commented on 2020-05-13 20:53

Hi, I'm getting this error when building:

ERROR: visual-studio-code.desktop was not found in the build directory and is not a URL.

Det commented on 2020-05-08 00:37

shrug yea, maintainers rarely wanna co-maintain (even me back when I was doing it).

mixedCase commented on 2020-05-08 00:35

@Det Yep, I can do the actual download and replace with the actual checksum just as easily, but doing an extra git commit and push would allow me to share it, just wanted to check if that was an option.

Det commented on 2020-05-07 23:09

@mixedCase, well.. on quick glance looks like you could maintain this locally with:

pkgver=$(curl -sL | grep -Pom1 "version \K[^)]*") # cut up from after "version " to the first ")" ("<h1>April 2020 (version 1.45)</h1>"), -m1: use only first result
pkgrel=1 # reset

Put it at the end of the PKGBUILD, and it's a portable piece of text that doesn't even conflict with anything.

mixedCase commented on 2020-05-07 22:50

@dcelasun Yes, and thank you for keeping it within reasonable bounds all this time!. I'm offering because I update packages within the hour (usually less), since I automate new release checks to fire an e-mail usually before an user files the package as out of date, edit the PKGBUILD, make some quick tests and ship it.

As for my personal reason, I've been working with VS Code much more often recently and the damned gear with the notification gets on my nerves, but I understand being hesitant.

Let me know if you do change your mind :)