bash-toolkit VS dotfiles

Ah a fellow person of culture :D

Maybe you will enjoy my "bash-toolkit" repo: https://github.com/adityaathalye/bash-toolkit which I've dubbed my "Swiss Army Toolkit" of functions-as-cmd-line-tools and useful-to-me patterns.

Which reminds me, I've collected more and should update the repo!

Source: https://github.com/adityaathalye/bash-toolkit/blob/master/bu...

The best part is sourcing pipeline-friendly functions into a shell session allows me to mix-and-match them with regular unix tools.

True, but you can represent that in the db as a a CLI invocation to run in a subshell.

The big gain from something like carapace or my theoretical SQLite-based completion system is faster startup time. I had to remove zsh-completions from my shell setup as it added too much to the startup time (https://github.com/bbkane/dotfiles/blob/master/zsh/README_no...)

"small embeddable dynamic languages" are usually used to configure or program other larger compiled applications. This is bes understood by example:

https://create.roblox.com/docs/tutorials/scripting/basic-scr... - make a mini game in Roblox

https://github.com/openresty/lua-nginx-module?tab=readme-ov-... - configure and extend NGINX

https://wezfurlong.org/wezterm/config/lua/general.html - make your terminal more useful (my personal config changes the tab color based on the process name - https://github.com/bbkane/dotfiles/blob/master/wezterm/dot-c...

https://m.youtube.com/watch?v=MQBr9hwf0BY - configure your text editor

I switched to iTerm2 a few years ago due to blurry fonts on zoom with Terminal.app . Wonder if that's still a problem?

A few months ago I switched to WezTerm and, after some config wrestling, I've been very happy using it (https://github.com/bbkane/dotfiles/tree/master/wezterm).

Yes, but it's super awkward to actually use day to day

I've got something of a wrapper script at https://github.com/bbkane/dotfiles/blob/8573e44d0f9fb5ddcbdc...

It doesn't read from files unfortunately, but https://openobserve.ai/ is very easy to set up locally (single binary) and send otel logs/metrics/traces to.

Here's how I run it locally for my little shovel project - https://github.com/bbkane/shovel#run-the-webapp-locally-with... .

Also linked from that README is an Ansible playbook to start OpenObserve as a systems service on a Linux VM.

Alternatively, see the shovel codebase I linked above for a "stdout" TracerProvider. You could do something like that to save to a file, and then use a tool to prettify the JSON. I have a small script to format json logs at https://github.com/bbkane/dotfiles/blob/2df9af5a9bbb40f2e101...

That sounds super similar my setup ( https://github.com/bbkane/dotfiles/tree/master/zsh ). I'll check out a few of those I haven't yet.

Here's a small script I use often to tag commits with Git.

It shows the current status, lists out the most recent tags, prompts for a new tab and message, and finally pushes.

Everything is colorized so it's easy to read and I use it quite often for Golang projects.

https://github.com/bbkane/dotfiles/blob/e30c12c11a61ccc758f7...

Ooh I'm doing this too, but with Python to add a "category" field (based mostly on description), nushell to munge the CSV into more CSVs so I can build html charts and tables with this script. in my opinion, transforming the two original CSVs (checking account and credit card history) into the html doc with all the charts is best done as this sort of pipeline so you can replace bits as you find better alternatives (for example I started with SQLite instead of nushell for the "child CSV" parts)

I use https://github.com/bbkane/dotfiles/blob/master/bin_common/bin_common/git_lines_changed_tsv.sh to turn this into a tsv which can then be charted by piping to https://github.com/bbkane/dotfiles/blob/master/bin_common/bin_common/scatterplot.py .