Package Details: vscodium-bin 1.95.3.24321-3

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: 311
Popularity: 6.11
First Submitted: 2020-09-23 18:58 (UTC)
Last Updated: 2024-11-26 20:34 (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 .. 5 6 7 8 9 10 11 12 13 14 15 .. 25 Next › Last »

Icelk commented on 2023-01-14 10:03 (UTC)

@fractalf No problem :) I only maintain this package, so it wasn't my decision. But I can change it :) I actually consider that to be a problem in the distro, as they should set default apps for all file types. We don't change the default. We just give another option. Would it be better if vscodium warned on install that you might have to run the xdg-mime command? Because we can't do that, because we don't know which .desktop file the user wants to default to. But can you right click on a folder and click "open with", or at least properties and there change the default handler?

fractalf commented on 2023-01-12 23:12 (UTC)

@Icelk Thank you for responding :)

Ok, I'm a bit curious about this, from a "I like to learn stuff" point of view. You say "believe", is this not your decision?

Here's my 5 cent about this. I just switched to EndeavourOS after 10 years using another distro. I'm super stoked! Just love the Arch pacman/aur etc

I install codium and next thing i know my short cut for opening Nemo opens codium. Then I plug in a usb-stick and codium also opens. wtf is this I'm thinking. I spend hours researching this and finally found out why. I'm not alone it seems: https://www.reddit.com/r/ManjaroLinux/comments/u45dpz/not_about_installation_when_i_plug_in_a_usb_stick/

So, yea, if I could choose between sane defaults here, I'd rather just very easily fix the context menu myself. Right-click file, open with other application, done.

Anyway, thanks a lot for this package! :)

Icelk commented on 2023-01-12 14:46 (UTC)

Hi @fractalf. Thanks!

I've actually answered this question before:

I believe this is done to add codium to the open-with context menu. If you want another app to open, you can always create your own .desktop file (and e.g. open the folder in you terminal of choice) or just remove the default open with choice using the xdg utilities (xdg-mime default nemo.desktop inode/directory).

fractalf commented on 2023-01-11 22:23 (UTC) (edited on 2023-01-11 22:25 (UTC) by fractalf)

Hi! There is a bug in this package that messes with 2 things on my EndeavourOS (Cinnamon)

  1. After install, inserting an USB stick opens vscodium (instead of Nemo)
  2. Pressing Win+E opens vscodium (instead of Nemo)

I tracked it down to this line in vscodium-bin.desktop

MimeType=text/plain;inode/directory;

This messes up the file /usr/share/applications/mimeinfo.cache after installing:

# Before install
> cat /usr/share/applications/mimeinfo.cache | grep inode
inode/directory=nemo.desktop;

# After install
> cat /usr/share/applications/mimeinfo.cache | grep inode
inode/directory=codium.desktop;nemo.desktop;

I'm not sure why this (inode/directory) was even added in the first place, but I'm sure this messes up at least these two things mentioned.

Cheers! :)

Edit: Yea and the fix is to remove inode/directory; from vscodium-bin.desktop, I tried this locally, build it and installed it and all was fine

BachoSeven commented on 2023-01-09 23:07 (UTC)

[managed to install it now, so maybe github just gave me garbage a few times, though I did try it on different connections as well]

BachoSeven commented on 2023-01-09 23:02 (UTC)

@Icelk It's still saying it's the wrong hash (actually looks like the has of the x86_64 file is back to the one you originally put in 1.74.2.23007-1).

wavetro commented on 2023-01-08 17:03 (UTC)

Is there a way to refresh any cached sums I might have? I'm still getting a validity check error for the main .tar.gz file

Icelk commented on 2023-01-07 17:11 (UTC)

Hey. The issues with the sums should be resolved now. Thanks for notifying me!

HelloImWar commented on 2023-01-07 15:27 (UTC) (edited on 2023-01-07 15:27 (UTC) by HelloImWar)

The binaries were uploaded to GitHub a few minutes ago, but the hashes for the binaries still need to be updated.

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 .. 25 Next › Last »