shrc VS prompt.gem

do I need to say it: 4x time faster. just minus some the cool parts and fallbacks are not that hard, like local keyword https://github.com/denisde4ev/shrc/blob/master/_fallback/local. and the consequences of not having local all around my repos unset-unseted-i and unset-seted-i that throws error if nested functions use i variable at the same time.

I already have lolwall in my bashrc, but I forgot the bricks

my aliases are alias cin='xclip -sel clip -r' cout='xclip -sel clip -o' for clipboard input/output (hi C++ programmers). And if its Wayland then it uses wl-copy or if have termux-clipboard commands. my entire file for detecting it is: https://github.com/denisde4ev/shrc/blob/master/clip-io

I wrote my own sh function aliased to cd.. and CD https://github.com/denisde4ev/shrc/blob/master/_loadable/_cd__.sh

you can see my __load_loadable function here https://github.com/denisde4ev/shrc/blob/master/_loadable/LOADABLE (sorry if my code is not simple)

My PC: Lenovo AIO; 21" touchscreen monitor; Arch+KDE. I'm happy witch my bashrc/shrc organization

And like many I've spent waaay too long messing around with my shell environment, which has wound up as ProfileGem, a modular shell environment manager, along with prompt.gem, my custom terminal prompt. Some features that stand out:

I've been using this library for years to make my terminal prompt more zippy. It takes advantage of a number of unusual techniques that folks might find interesting.