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

Git Clone URL: https://aur.archlinux.org/visual-studio-code-bin.git (read-only)
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
Submitter: dcelasun
Maintainer: dcelasun
Last Packager: dcelasun
Votes: 815
Popularity: 22.903079
First Submitted: 2017-12-18 19:14
Last Updated: 2019-04-11 18:56

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 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.

  • 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 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.

  • 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.

  • What happened to visual-studio-code?

It got renamed with a -bin suffix. If you have the original package installed, you will be prompted to delete it when you install this package for the first time.

Latest Comments

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

Rainer commented on 2019-04-07 10:02

I'm on arch 32Bit. I downloaded the snapshot and installed the package with makepkg -sirc. Everything worked fine. If I start either from the menu or with "code" from the terminal it starts but all I get is a blank screen. Did I missed something?

elgs commented on 2019-04-04 20:24

1.33.0-2 works! Thanks @dcelasun.

dcelasun commented on 2019-04-04 20:22

Sorry, fixed.

elgs commented on 2019-04-04 20:20

:: Searching databases for updates...
:: Searching AUR for updates...
:: 1 Packages to upgrade.
1  aur/visual-studio-code-bin  1.32.3-1 -> 1.33.0-1
==> Packages to not upgrade: (eg: 1 2 3, 1-3, ^4 or repo name)
==> 


install: cannot stat '/home/elgs/.cache/yay/visual-studio-code-bin/src/VSCode-linux-x64/resources/app/LICENSE.txt': No such file or directory
==> ERROR: A failure occurred in package().
    Aborting...
Error making: visual-studio-code-bin

dcelasun commented on 2019-04-04 13:19

@melkopisi, @HerHde, there are plenty of solutions to this problem, all of them a quick search away. For example:

There should be more for other DEs as well.

HerHde commented on 2019-04-04 12:59

Well, about the "inode/directory" link: It interferes with almost every software on my freshly installed system (Manjaro), including Nautilus and Firefox.

melkopisi commented on 2019-04-03 20:21

butother apps suggest open their file in visual studio code instead from nautilus like Android studio because it has the priority above nautilus to open folders

any idea how to fix this?

dcelasun commented on 2019-04-03 12:53

@melkopsi, that's needed for opening directories with VS Code. If it interferes with Nautilus, that must be a configuration issue on your end. It works fine for me here.

melkopisi commented on 2019-04-03 12:21

Please can you stop adding "inode/directory" to the MimeType because it interferes with nautilus?

dcelasun commented on 2019-03-22 20:50

@albertvaka that has been asked and answered several times, read the comments please.