bash-cache VS mini-prompt

This is usually what a caller expects, but it's definitely surprising when it isn't. I encountered this with my bash-cache library because simpler approaches to caching commands will use command substitutions which turns out to be lossy (because it drops any trailing newlines).

Is the goal of your cache function to cache a command if it's been run before? If so you might like to use my bash-cache library :) Even if it's not quite what you're looking for you can poke around the code for some inspiration, it implements a function decorator pattern and demonstrates some hairy uses of eval.

For another pure-bash solution (though it writes to disk, not in-memory arrays) check out my bash-cache library :) it's an older project that motivated bkt but I still use both. There's some terrifying bash patterns in bash-cache as well!

I'm pretty proud of my bash-cache utility, which implements a decorator pattern in Bash. Define a function, pass it to bc::cache, and like magic the function is wrapped with a caching layer.

You can find the needed files and instructions in my PR https://github.com/Pocco81/MiniPrompt/pull/2

I have this project on GitHub called MiniPrompt that's basically a minimalist and fast shell prompt with the main idea of the user using the various features that it has relative to the current session/shell.

I recently opened a repo for a little project of mine (https://github.com/kdav5758/MiniPrompt) and what I did for the first releases has to create like 3 tags as "v" and then created a release of the last tag as the same: "v-alpha"

Hello everyone! I spent the last 24hrs writing this simple project. MiniPrompt (minimalist prompt), is a minimalist bash prompt that has several functionalities and is oriented to those who want something more native to bash and allows a wide variety of things to customize it while still being *lightning fast*.