Arch Linux User Repository

New Command Available in 1.95.0-2

Now there is a new command /usr/bin/code-features-update that can update the patch to keep up with the official vscode release. You can use this command to manually update the patch when this package is out of date or some extensions don't work after an update in extra/code.

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:

1. Syncs proposed APIs with the latest vscode release. Some extensions don't work in code oss because some specific APIs are not enabled in product.json.
2. Enable built-in settings sync feature.
3. Disable telemetry.
4. Use ~/.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:

1. Some extensions (e.g. Pylance) require to use the data directory to work.
2. Isolate settings sync data from the OSS version. People may want to install this package because they want to unlock some proprietary extensions, and may have some specific settings that only works with these extensions. Besides, this package will enable built-in sync feature, so isolating the settings may avoid some potential problems such as messing up your synced settings.

If you don't like this behavior, simply create a symlink.

About proprietary extensions

Proprietary extensions are not guaranteed to work, because some extensions will actively detect whether the current running environment is the official vscode release, and it's very hard to bypass their detection at all time.

If some extensions don't work, try:

1. Run update.py in the project root. This scripts will update the patch to match the latest vscode release. Then execute makepkg -fsi to rebuild and install this package.
2. Switch over a FOSS alternative, for example Pylance -> Basedpyright, C/C++ -> Clangd

Should maybe optionally depend on icu69 for liveshare to work with the code package, since it is only usable with this package as a feature not available in the code build normally.

@sainnhe the real issue it's here https://github.com/MicrosoftDocs/live-share/issues/4669 and install the icu69 aur package it's the solution.

I have tried icu70 and work, it don't replace the icu package and you can have installed icu and icu70 together.

@sainnhe You're welcome!

@GFdevelop: I found the exact issue on github, looks like a packaging issue of community/code.

https://github.com/MicrosoftDocs/live-share/issues/4229

@jongeduard: Thanks! It should be fixed now.

ERR command 'liveshare.startFromWelcomeContent' not found: Error: command 'liveshare.startFromWelcomeContent' not found

Package or extension error?

"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??

My bad. Sync should be fixed now.

Looks like sync no longer works in 1.65.1, does anyone manage to get it work?

Sync works, marketplace doesn't. (YES IT DOES)

UPDATE: silly me should have installed code-marketplace too.