streamdeck-ui VS fish-shell

Unfortunately, the StreamDeck doesn't emulate a standard USB HID device, so it needs a driver running in the background to detect button presses and do things like generate keystrokes or call Keyboard Maestro macros.

There's streamdeck-ui (https://timothycrosley.github.io/streamdeck-ui/), which is an open-source alternative, but it at first glance it seems to be only for Linux).

There are a bunch of other macro/launcher pads like the StreamDeck that DO act as standard USB HID keyboards, though, and those should work fine with Keyboard Maestro using keyboard shortcut triggers.

Found that one which seems to work with older models. https://github.com/timothycrosley/streamdeck-ui or https://flathub.org/apps/com.feaneron.Boatswain

what OS do you have on ur pi? from what i know stream deck is only compatible with Windows and MacOS, you’d have to do a special setup to use it with Linux

Not sure if that keyboard has open source editing software, but Elgato Stream Deck certainly does.

tbh I didn’t have a problem with the official Windows app so I can’t say anything about that much

But under Linux I used this

https://timothycrosley.github.io/streamdeck-ui/

Works pretty well by my experience under Debian. There are some edge cases like Wayland (see the issues) though.

The only tip I'd have would be for Wayland users who suffer from not having global shortcuts work with OBS: obs-cli with obs-websocket have you covered. Set a keyboard shortcut or Stream Deck button (using streamdeck-ui) to execute an obs-cli command and you're done.

Anyone have any experience with the ElGato Keylights on Linux? I use Ubuntu 22.04. I have stream deck that I use with Streamdeck-ui and I wanted to know if anyone uses these lights with a cli program that would allow me to control them? On, Off, brightness, etc?

Thanks for the info, I wasn't aware of the Stream Deck. It is also supported on Linux by Open Source library and app. Very tempting.

https://github.com/timothycrosley/streamdeck-ui/

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