Dependencies of gtk2 is outdated. As you can see, VSCode shifted from gtk2 to gtk3.
https://github.com/Microsoft/vscode/commit/2e6a761f8c225ae7aad144c071414bb080916ad9
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: | 1462 |
Popularity: | 13.84 |
First Submitted: | 2017-12-18 19:14 (UTC) |
Last Updated: | 2024-11-15 11:08 (UTC) |
« First ‹ Previous 1 .. 47 48 49 50 51 52 53 54 55 56 57 .. 78 Next › Last »
Dependencies of gtk2 is outdated. As you can see, VSCode shifted from gtk2 to gtk3.
https://github.com/Microsoft/vscode/commit/2e6a761f8c225ae7aad144c071414bb080916ad9
On Manjaro Deepin, the dock icon tends to clear itself from the dock, see: https://github.com/Microsoft/vscode/issues/49183
Under the hood, deepin seems to be using some elements inherited from Gnome. This could be related to that.
This package stores lots of stuff in ~/.config/Code/ that doesn't seem to belong in $XDG_CONFIG_HOME.
In particular:
Cache/, CachedData/, CachedExtensions/, GPUCache/, logs/ : user-specific cached data should be in $XDG_CACHE_HOME ($HOME/.cache by default)
'Local Storage'/, Backups/, User/workspaceStorage/, Cookies, Cookies-journal, machineid : This looks like stuff that belongs in $XDG_DATA_HOME ($HOME/.local/share by default)
storage.json : I'm not sure about this but it smells fishy :P
For a reference, see https://wiki.archlinux.org/index.php/XDG_Base_Directory_support and https://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html and https://github.com/Microsoft/vscode/issues/3884
The information you share is very useful. It is closely related to my work and has helped me grow. Thank you! http://instagquotes.com
Installing this package changed my xdg default for folders. xdg-open
, which is also used by other programs, now opens VS Code for folders instead of my previous default (nautilus).
I don't think a software installation should change defaults. However, I don't know if this is a bug of this package or an upstream bug.
Manually restoring the previous default is possible with:
xdg-mime default org.gnome.Nautilus.desktop inode/directory
@spacepluk: Fixed, thanks.
:: Checking visual-studio-code-bin integrity... ==> ERROR: provides contains invalid characters: ',,'
https://github.com/Microsoft/vscode/commit/2e6a761f8c225ae7aad144c071414bb080916ad9
As you can see, VSCode shifted from gtk2 to gtk3.
@Batou: This package follows upstream. Feel free to use other packages and/or a personal settings.json
.
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.