Package Details: vscodium-bin 1.91.1.24193-1

Git Clone URL: https://aur.archlinux.org/vscodium-bin.git (read-only, click to copy)
Package Base: vscodium-bin
Description: Binary releases of VS Code without MS branding/telemetry/licensing.
Upstream URL: https://github.com/VSCodium/vscodium
Licenses: MIT
Conflicts: vscodium
Provides: codium, vscode, vscodium
Submitter: ckatri
Maintainer: sperg512 (Icelk)
Last Packager: Icelk
Votes: 291
Popularity: 13.60
First Submitted: 2020-09-23 18:58 (UTC)
Last Updated: 2024-07-11 19:00 (UTC)

Pinned Comments

sperg512 commented on 2021-05-12 00:31 (UTC) (edited on 2024-06-04 15:14 (UTC) by sperg512)

@Icelk set up a script that checks for new releases and pushes updates if there are any new ones. I believe it runs every hour so there's no need to flag OOD, unless there's something that needs changed with the PKGBUILD.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 .. 23 Next › Last »

manuth commented on 2023-06-09 10:49 (UTC) (edited on 2023-06-09 11:02 (UTC) by manuth)

The vscodium-bin.sh file currently does not work properly. The fact that "$@" is passed to vscodium after $CODE_USER_FLAGS seems to cause vscodium to ignore the specified directory/file to open.

This can be fixed by - much like in visual-studio-code-bin - by passing the "$@" first and $CODE_USER_FLAGS after.

LRitzdorf commented on 2023-05-13 13:20 (UTC)

Looks like the rendering issue is fixed in 1.78.2. Thanks for the quick update!

macwen commented on 2023-05-11 04:41 (UTC)

Rendering also seems to be broken for the edge devtools in version 1.78.1.23130-1. Rollback to version 1.77 seems to fix it.

LRitzdorf commented on 2023-05-10 23:48 (UTC)

As a heads-up, it looks like rendering is somehow broken in v1.78.1. I updated (1.77.3.23102-1 -> 1.78.1.23130-1) earlier today, and upon restarting, the Release Notes page and PDF previews from the LaTeX Workshop extension are simply blank.

The Interactive Editor Playground seems to work, and actual source code is also rendered successfully, so I'm not quite sure what's going on here.

Gert-dev commented on 2023-03-16 16:20 (UTC)

Awesome, thanks!

Icelk commented on 2023-03-14 17:12 (UTC)

@Gert-dev I've just implemented fixes to all your issues. The file is ~/.config/codium-flags.conf. StartupNotify=false.

Gert-dev commented on 2023-03-13 19:10 (UTC) (edited on 2023-03-13 19:10 (UTC) by Gert-dev)

Separately, is it possible that using ~/.config/electron-flags.conf or ~/.config/code-flags.conf are not supported?

The VSCodium issue tracker mentions packaging usually handles this, and indeed, the visual-studio-code-bin seems to do that.

Gert-dev commented on 2023-03-13 18:40 (UTC) (edited on 2023-03-13 18:53 (UTC) by Gert-dev)

Would it be possible to disable StartupNotify and make it StartupNotify=false in the desktop files? Having it set to true is resulting in this mutter issue and upstream VSCode also sets it to false.

Icelk commented on 2023-02-08 18:45 (UTC)

@motherofmilk Indeed

motherofmilk commented on 2023-02-08 17:46 (UTC)

@Icelk I removed everything, reinstalled vscodium to check if the issue was still there (it was), installing the marketplace package didn't fix it, but the features package however did. That's strange.