gum VS pueue

The inspiration for this is the neat project gum (https://github.com/charmbracelet/gum) but I would deliver OS native apps vs. shell scripts.

Instantly reminded me of https://github.com/charmbracelet/gum. Maybe you can take inspiration from there (NodeJS so can't steal much code).

Hey, this came to my mind a few times before but I never pursued it further, but now I'm wondering: Has anybody shared a button mapping to use Konsole and Bash more conveniently? A few things like more back a word or move forward a word and delete a word come to my mind which I use regularly on my desktops. The Deck as definitely enough buttons and with some clever invocations of gum you'd almost have a simplistic file manager at hand.

Been writing scripts for a couple of workflows using gum. Loading stash based on branch name and rebasing feature branches. Mostly to learn more about git and play around with the underapprecated CLI front-end engineering/design.

Gum ! https://github.com/charmbracelet/gum

That said, no idea if there's a fish builtin that does this, but I use Gum for this sort of thing.

https://github.com/charmbracelet/gum is purpose-built for this, and easy to integrate into shell scripts and the like.

You can probably do a good subset it in bash, it's just a nicer interface with a lot of configurability and several convenience features.

I'm generally a big fan of showing alternatives: https://github.com/Nukesor/pueue/?tab=readme-ov-file#similar...

Would you be willing to write a proper guide on how to do all of these things in bash? It would be great to have this as guide an alternative inside the Pueue wiki and link to it. It'll help people to make a more informed decision on whether they need this tool or not.

there is a command line manager for long running tasks called Pueue. It is released into Nix, Arch, Alpine, Void, etc, but not for Debian based distros. I know that releasing into Debian is a bit more challenging, but I just wanted to ask if anybody here might be interested in packaging it. Just as a disclaimer, I am not the author of this project, just a regular user.

This one? https://github.com/Nukesor/pueue

How about this: https://github.com/Nukesor/pueue/? I have it bookmarked from a thread here from few years back and never got to test it eventually, but maybe it will serve your purposes?

Multiplexing is great for your multiple outputs, but I would highly recommend using pueue & pueued for job control. Lets you organize your background jobs into groups which can be paused, resumed, etc. Also lets you act on jobs from different terminals w/the pueue interface.

pueue -- a queue for tasks, running in background

For the command that takes a long time to complete, I always use pueue to run. This thing let you run multiple commands in order and can schedule the execution later which is really helpful to my workflow.

That said, you're basically building pueue. https://github.com/Nukesor/pueue/blob/main/ARCHITECTURE.md might give you some pointers. From reading it, there seems to be a mishmash of tokio stuff, and then everything gets serialised onto an MPSC channel (that's serviced by TaskHandler, on a single thread that's also responsible for polling for finished processes etc, every 200ms).

exchange for pueue and you can even queue them up.

This is the only one I know of: https://github.com/Nukesor/pueue