glava VS fish-shell

Sounds like a job for GLava instead

glava an overkill gpu accelerated audio visualizer for the desktop Example: https://streamable.com/dgpj8

It was just a plug-in for Glava (https://github.com/jarcode-foss/glava) not really worth sharing imo.

[glava](https://github.com/jarcode-foss/glava) closes when I close the terminal, even after running it with the appended `&`. How to keep it running?

A lot of those soundwave things, etc. are just dedicated sound visualizers stuck onto the desktop - in most Linux environments you can put ANY program onto your desktop, not just a static picture. Something like glava (in fact I think it has a desktop option out of the box).

No, but alot of the functions can be through separate applications, per-monitor wallpapers can be done through hydrapaper, visualizers for music can be done through glava, and the stats readouts can be done through conky.

It's glava

GLava?

I've been trying to gather glava working. It seems like it's not being maintained any more, as there are a few compiling problems, but there are merge requests there that fix those. glava seems to run fine on my desktop, but won't run as an obs plugin. It segfaults when trying to load the‏‏‎‏‏‎‏‏‎‏‏‎­OpenGL libraries. Here's the relevant code from glx_wcb.c: typedef XID GLXFBConfigID; GLXFBConfig* (glXChooseFBConfig) (Display dpy, int screen, const int* attribList, int* nitems); static void* resolve_f(const char* symbol, void* gl) { void* s = NULL; if (gl) s = dlsym(gl, symbol); if (!s) { fprintf(stderr, "Failed to resolve GLX symbol: %s\n", symbol); glava_abort(); } return s; } And then this is in the init function: #define resolve(name) do { name = (typeof(name)) resolve_f(#name, hgl); } while (0) resolve(glXChooseFBConfig); I've only shown the first function that it tries to load, glXChooseFBConfig, since it fails on all of them. The call to dlsym() doesn't fail though (s gets returned), and I find that confusing. All this works just fine when running glava out of a console. I feel like I don't know enough about dynamic library linking to figure out what's going wrong. Any ideas?

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