hunter VS just

Yeah, that is unfortunately my experience too. There are ranger-like alternatives Hunter and lf. I have tried to switch a couple of times but my config for ranger is pretty heavily customised and I keep going back to it. I just mash ctrl-c if the previewer locks up the UI and it unlocks it.

sad CLI search and replace | Space Age seD tcount Count your code by tokens, types of syntax tree nodes, and patterns in the syntax tree. A tokei/scc/cloc alternative. nushell A new type of shell fclones Efficient Duplicate File Finder hunter The fastest file manager in the galaxy! teip Select partial standard input and replace with the result of another command efficiently cb Command line interface to manage clipboard semiuniq A uniq-like tool for removing nearby repeated lines in a file" dua-cli View disk space usage and delete unwanted data, fast. htmlq Like jq, but for HTML. pipecolor A terminal filter to colorize output crowbook Converts books written in Markdown to HTML, LaTeX/PDF and EPUB delta A viewer for git and diff output mdcat cat for markdown pueue Manage your shell commands. gitui Blazing 💥 fast terminal-ui for git written in rust 🦀 pipr A tool to interactively write shell pipelines. rename Rename your files using your favorite text editor bropages Highly readable supplement to man pages from http://bropages.org. Shows simple, concise examples for commands with syntax highlighting. html2md convert simple html documents into markdown bk Terminal Epub reader rs A safe Rust crate for working with the Wayland clipboard. viu Simple terminal image viewer written in Rust. alacritty A cross-platform, OpenGL terminal emulator. wezterm A GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust

Hunter is the best ive found. https://github.com/rabite0/hunter It previews images, pdfs and lots more. It's also written in rust.

I don't like makefiles, but I've been enjoying justfiles: https://github.com/casey/just

I started using just [0] on my projects and have been very happy so far. It is very similar to make but focused on commands rather than build outputs.

Define your recipes and then you can compose them as needed.

[0] https://github.com/casey/just

just - https://github.com/casey/just

Welp there is absolute chaos in that thread -- guess it's not an April Fools joke.

I wonder if relying on CI for anything other than provisioning machines is a mistake -- maybe we should have never moved from doing things from local scripts written in $LANGUAGE.

That said, I'm probably biased since I'm a massive fan of things like `make` and more appropriately for the current age, `just`[0]

[0]: https://github.com/casey/just

> When a command has some cognitive requirements I create a script with some ${1:-default} values and I store them all in $PATH enabled local/bin

I would consider using just for this:

https://github.com/casey/just

Your coworker's experience is more principled: Make is a mediocre tool for executing commands. It wasn't ever designed for that. Although it is pretty common to see what you are mentioning in projects because it doesn't require installing a dependency.

For a repo where an easy to install (single binary) dependency is a non-issue, consider using just. [1] You get `just -l` where you can see all the command available, the ability to use different languages, and overall simpler command writing.

[1] https://github.com/casey/just

This is fantastic, but I'd say that this solution is somewhat in response to this open issue from 2019:

https://github.com/casey/just/issues/429

I really wish just was included as a package in distributions.

So far, I didn't work on new features at all but on stabilizing the ground for further development: 1. CMake lists and modules were rewritten a lot, now managing builds and their configurations is much lesser pain. 2. Brought in Justfile for regular tasks, and it's great, no less. 3. Linters, formatters, analyzers for almost all the code (except for Janet for now, as because of it being a niche and young technology, it didn't get enough attention yet). 4. ECS stub. Now runtime class doesn't look like a god object. 5. Started writing unit tests which didn't happen with my personal projects before and maybe indicates how serious am I about this one :D 6. Some of previously hardcoded data has been moved to INI files. Now, if I release the game in 10 years, and in 10 more years some eccentric person decides to make a variant of it, it will be slightly simpler.

i've grown to like this for my personal projects. https://github.com/casey/just