@jongeduard: Thanks! It should be fixed now.
Search Criteria
Package Details: code-features 1.89.0-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/code-features.git (read-only, click to copy) |
---|---|
Package Base: | code-features |
Description: | Unblock some features in Code OSS |
Upstream URL: | https://github.com/microsoft/vscode |
Keywords: | vscode |
Licenses: | unknown |
Conflicts: | code-features |
Provides: | code-features |
Submitter: | sainnhe |
Maintainer: | sainnhe |
Last Packager: | sainnhe |
Votes: | 52 |
Popularity: | 0.22 |
First Submitted: | 2021-04-06 00:46 (UTC) |
Last Updated: | 2024-05-07 07:34 (UTC) |
Dependencies (4)
- code (visual-studio-code-cli-binAUR, visual-studio-code-binAUR, vscodius-binAUR)
- org.freedesktop.secrets (keepassxc-gitAUR, gnome-keyring-gitAUR, bitw-gitAUR, pass-secrets-gitAUR, keepassxc-allow-aur-extension-originAUR, keepassxc-allow-aur-extension-origin-binAUR, gnome-keyring, keepassxc, kwallet, kwallet5)
- python (python37AUR, python311AUR, python310AUR)
- icu69AUR (icu69-binAUR) (optional) – for MS-vsliveshare.vsliveshare extension to work
Required by (1)
- code-marketplace (optional)
Sources (3)
sainnhe commented on 2022-05-05 12:53 (UTC)
GFdevelop commented on 2022-04-20 08:37 (UTC)
ERR command 'liveshare.startFromWelcomeContent' not found: Error: command 'liveshare.startFromWelcomeContent' not found
Package or extension error?
jongeduard commented on 2022-04-15 18:52 (UTC) (edited on 2022-04-15 18:54 (UTC) by jongeduard)
"Writing login information to the keychain failed with error 'GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.secrets was not provided by any .service files'."
Since very recently I haved been seeing this error in Code OSS. A bit of searching around made me clear that I NEED to have gnome-keyring. Otherwise this error is the result. And 'pacman -Qi' shows that gnome-keyring is an optional dependency of code-features, while not being any dependency of code itself or code-marketplace. And indeed installing gnome-keyring fixes the issue. (I've may have had gnome-keyring before as a depencency of other packages, but things change and a 'pacman -Rs $(pacman -Qdtq)' that I run regularly may have removed it as currently no other package on my system seems to need it anymore - I use Xfce, not GNOME anyway.)
So: Why is gnome-keyring an defined as an optional depencency for this package while it should be a required one??
sainnhe commented on 2022-03-10 12:46 (UTC)
My bad. Sync should be fixed now.
sainnhe commented on 2022-03-09 08:26 (UTC) (edited on 2022-03-09 08:26 (UTC) by sainnhe)
Looks like sync no longer works in 1.65.1, does anyone manage to get it work?
barraponto commented on 2021-11-30 19:27 (UTC) (edited on 2021-11-30 19:38 (UTC) by barraponto)
Sync works, marketplace doesn't. (YES IT DOES)
UPDATE: silly me should have installed code-marketplace too.
billypilgrim commented on 2021-11-30 18:33 (UTC)
This isn't working for me at the mo. I still can't access the marketplace.
sainnhe commented on 2021-10-13 06:38 (UTC)
@huantian: Isn't it already depending on it?
huantian commented on 2021-10-13 03:41 (UTC)
Perhaps this package should be marked as depending on Code OSS, as it fails to install without it?
Pinned Comments
sainnhe commented on 2024-05-17 03:39 (UTC) (edited on 2024-05-17 03:39 (UTC) by sainnhe)
About this package
This package installs a hook that will patch product.json every time the code package is updated. The patch basically does the following:
~/.vscode
and~/.Code
instead of~/.vscode-oss
and~/.Code OSS
.You might be confused why this package changes the data directory. There are two reasons:
If you don't like this behavior, simply create a symlink.
About the maintainance
I'm a vim user, and I rarely use vscode. I created this package simply for fun. And for some reasons, I'm not using Arch Linux as my daily driver anymore.
I'll continue to maintain this package for a while until my old Arch Linux machine retires. If you want to become a maintainer of this package, feel free to contact me (i@sainnhe.dev).
Updating the package is very simple, you just need to run
update.py
in the root of this repository. The script will automatically updatepatch.json
which contains the patch data.