@dcelasun great work, thanks!
Have you thought about including libdbusmenu-glib as an optional dependency? It allows vs code to pass the menu through DBus, makes KDE global menu work.
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.87 |
First Submitted: | 2017-12-18 19:14 (UTC) |
Last Updated: | 2024-11-15 11:08 (UTC) |
« First ‹ Previous 1 .. 42 43 44 45 46 47 48 49 50 51 52 .. 78 Next › Last »
@dcelasun great work, thanks!
Have you thought about including libdbusmenu-glib as an optional dependency? It allows vs code to pass the menu through DBus, makes KDE global menu work.
@adlerdias: Seems to be a Windows-only bug as stated here: https://github.com/Microsoft/vscode/issues/58032#issuecomment-419013555
Nevertheless 1.27.1 is expected to be released pretty soon.
The package has been marked as outdated, but the maintainer must wait until 1.27.1 because of the bug:
Bug: Dragging files and other draggable items causes complete lock Posted a bug in detail on https://github.com/Microsoft/vscode/issues/57766
Quick Note: this bug only happens when running code from /opt/visual-studio-code/code
, and not the ones in /opt/visual-studio-code/bin/code
and /usr/bin/code
Not 100% sure if this is a pkgbuild issue or not as I'm not too versed in pkgbuilds (not sure why there are two binaries in the first place?)
@clockface, if I understand that thread correctly, this affects a single key combination and the workaround is non trivial: It introduces a new dependency and even then it doesn't work for everyone. GTK 3.24 is scheduled for release in September, so I'd rather wait a few weeks for that.
But if you or anyone else can come up with a simple, non-invasive patch I'd be happy to take a look.
@dcelasun, any plans for a work around to this issue:
https://github.com/Microsoft/vscode/issues/48480
until gtk 3.24 is released
@LChris314 fixed, thanks!
Thanks for the quick update! I suppose the following two lines should be removed from the PKGBUILD?
14 makedepends=(patchelf)
24 noextract=("glibc-2.27-3-${CARCH}.pkg.tar.xz")
Updated to 1.26.1, which removes the various glibc workarounds and replaces gtk2 with gtk3.
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-open
uses 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.