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

Git Clone URL: https://aur.archlinux.org/visual-studio-code-bin.git (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: https://code.visualstudio.com/
Licenses: custom: commercial
Conflicts: code
Provides: code, vscode
Submitter: dcelasun
Maintainer: dcelasun
Last Packager: dcelasun
Votes: 1465
Popularity: 14.57
First Submitted: 2017-12-18 19:14 (UTC)
Last Updated: 2024-11-15 11:08 (UTC)

Required by (20)

Sources (7)

Pinned Comments

dcelasun commented on 2017-11-15 06:20 (UTC) (edited on 2020-02-06 21:33 (UTC) by dcelasun)

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

« First ‹ Previous 1 .. 59 60 61 62 63 64 65 66 67 68 69 .. 78 Next › Last »

dcelasun commented on 2017-04-13 14:24 (UTC)

Sure, I'll update the description with the next update.

<deleted-account> commented on 2017-04-13 14:23 (UTC)

If I search with `yaourt -Ss "visual studio code"` it won't show me this entry probably because there's no mention of the name in the description. Could you include "Visual Studio Code" or similar somewhere in the description so that more people can find the package? It found only -git and -oss versions, so I thought there must be a normal version without any postfix and googled it. Thanks for packaging. UPD. Regarding emails & such: you're a rock star in scope of the AUR, this package has 40+ popularity rate and 351 votes currently. So yeah, I'd expect a decent response immediately when the package doesn't build. Just deal with it.

BunBum commented on 2017-04-07 18:21 (UTC)

No problem. Everything cool ;-)

dcelasun commented on 2017-04-06 17:26 (UTC)

Sorry, please don't take it personally. It just gets a bit overwhelming sometimes. I thought your comment was "useless" (maybe not the best choice of words), because the package was already flagged out of date so it didn't add anything new, it was basically just another "me too" which is not helpful. Anyway, it should work fine now.

BunBum commented on 2017-04-06 17:15 (UTC)

Useless? Sorry I didn't knew that it is useless for you to tell you that the package could not be installed on my machine. I installed it the first time today on my machine and didn't knew that there was an update today. Also I didn't knew that 1 person flagged it out of date and 3 persons wrote an email. For me I just wanted to install this package today on my new machine and saw this error coming up. Nothing more. I'm sorry that I disturbed you and will not annoy you anymore.

dcelasun commented on 2017-04-06 16:47 (UTC) (edited on 2017-04-06 16:48 (UTC) by dcelasun)

Guys, please. A hotfix was released 10 seconds ago and we already have: - 1 person flagging it out of date, - 3 different people emailing me to update it, - Yet another person posting a useless comment with a failed checksum. So please calm down and stop spamming me. It's a minor release of a text editor, it's not the end of the world. Hell, the fixes are Windows/OSX only. Updated to 1.11.1.

BunBum commented on 2017-04-06 16:04 (UTC)

==> Validating source_x86_64 files with md5sums... code_x64_1.11.tar.gz ... FAILED visual-studio-code.desktop ... Passed ==> ERROR: One or more files did not pass the validity check! ==> ERROR: Makepkg was unable to build visual-studio-code.

ram4nd commented on 2017-03-24 10:08 (UTC)

There are some symbols missing in the menu, perhaps a dependency on a font package or something?

Moter8 commented on 2017-03-19 12:04 (UTC)

If you were wondering, like me, how the command/bin is actually called, it's `code`.

dcelasun commented on 2017-03-02 08:14 (UTC)

Checksums were valid for 1.10, but they published a hotfix (1.10.1), which is why I just pushed an update.

« First ‹ Previous 1 .. 59 60 61 62 63 64 65 66 67 68 69 .. 78 Next › Last »