udiskie VS fish-shell

The most common approach (though a bit different) to get write access for users is probably using udisks[1]/udiskie[2] which use udev and polkit [3]. udiskie even supports luks unlocking [4].

https://github.com/coldfix/udiskie looks close, but does it work without desktop environments? Is there alternatives to udiskie that doesn't require desktop environments and supports unlocking LUKS encrypted volumes?

Based on https://github.com/coldfix/udiskie/blob/master/doc/udiskie.8.txt and https://github.com/coldfix/udiskie/issues/66#issuecomment-289204539, you probably need to create a configuration for the encrypted hard disk in the file ~/.config/udiskie/config.yml. For example, as follows.

For example, I typically ran things like lxpolkit, nm-applet, redshift, udiskie and xfce4-power-manager when I used i3.

By running udiskie in your i3 session, for example.

This. There is also udiskie, a GUI tool with notification icon, support for unlocking encrypted partitions, powering off USB devices, and so on.

I've used udiskie to handle removable drives in i3.

Reminds of the note at the bottom of Fish's releases. It's there because the build system cannot determine the current version for some reason. Hopefully that will go away now that they have switched to a different language / build system. The custom tarball is used by Arch Linux at the very least.

https://github.com/fish-shell/fish-shell/releases/tag/3.7.1

https://github.com/fish-shell/fish-shell/issues/7772#issueco...

https://gitlab.archlinux.org/archlinux/packaging/packages/fi...

A recent practical example of the former: the fish shell re-wrote incrementally from C++ to Rust, and is almost finished https://github.com/fish-shell/fish-shell/discussions/10123

An example of the latter: c2rust, which is a work in progress but is very impressive https://github.com/immunant/c2rust

It currently translates into unsafe Rust, but the strategy is to separate the "compile C to unsafe Rust" steps and the "compile unsafe Rust to safe Rust" steps. As I see it, as it makes the overall task simpler, allows for more user freedom, and makes the latter potentially useful even for non-transpiled code. https://immunant.com/blog/2023/03/lifting/

And this discussion from November has an update on the progress: https://github.com/fish-shell/fish-shell/discussions/10123

We're using bash as our terminal shell for now (it is standard in many distros) but it is not the only one out there. If you want to test out zsh, fish or oh-my-zsh, you will see that there are a few differences and the features are usually the main differentiator. Try that, poke around.

They have a variety of reasons to move to rust, as outlined in their original rust discussion[1]. Mostly around finding other contributors, and adding an async/parallel mode they're comfortable with.

[1] https://github.com/fish-shell/fish-shell/pull/9512