| 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: | 1418 |
| Popularity: | 21.65 |
| First Submitted: | 2017-12-18 19:14 (UTC) |
| Last Updated: | 2024-04-13 14:03 (UTC) |
I have to correct myself: Have not used VSCode on this Arch install for a while, but the arguments passed still seem to get lost if they are put after $CODE_USER_FLAGS.
code . only works for me if I change line 11 of /opt/visual-studio-code/bin/code to look like follows:
exec /opt/visual-studio-code/bin/code "$@" $CODE_USER_FLAGS.
Can we take that change into this AUR package, or is there a negative side to this that i am not aware of?
Ever since v1.69 the when launching Code the running app is displayed as a separate, unstyled app icon in my dock instead of being tied to the original icon. In this screenshot you can see the VS Code icon on the left. When I clicked that icon the grey gear icon shows up and is the running instance of VS Code. The StartupWMClass of the .desktop file is correct. Not sure if this should be reported here or upstream.
EDIT: This looks like an issue with VS Code itself under Wayland.
I don't understand why this is flagged out of date. I can see that it is perfectly matching to the latest version of vscode we have
@digital wow, thanks a bunch! I tried it without sudo and it suddenly worked!
Good to know!
@Smokus do not run yay with sudo
I am fairly new to the Linux world. I ran the following command to install VS Code:
sudo yay -S visual-studio-code-bin, but I following error:
Avoid running yay as root/sudo.
:: Checking for conflicts...
:: Checking for inner conflicts...
[Repo:1] lsof-4.95.0-1
[Aur:1] visual-studio-code-bin-1.68.1-1
:: (0/1) Downloaded PKGBUILD: visual-studio-code-bin
-> error fetching visual-studio-code-bin: fatal: could not create work tree dir > 'visual-studio-code-bin': Permission denied
context: exit status 128
Installing "code" package from official Arch Repo works just fine. Any help is appreciated.
i don't know if help, but with this command is a easy way to know about last version:
curl 'https://code.visualstudio.com/sha/download?build=stable&os=linux-deb-x64' -s -L -I | grep 'filename=' | cut -f2 -d'"' | cut -f2 -d'_' | cut -f1 -d'-'
Because it's been more than a year since upstream enabled the sandbox on Linux and it's time this package caught up.
It doesn't start anymore without manually adding --no-sandbox to ~/.config/code-flags.conf now.
Why was this removed from the .desktop files?
Added icu69 to optdepends.
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!)
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.
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.
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.xdg-openuses vscode, not my file manager! How do I fix this?Install shared-mime-info-gnome. Also see this reddit thread.
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.
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.
No, you won't get a reply. Please stop doing this. Leave a comment here instead and be patient.