myterminal-cli VS twiner

Having gone through all this, (I may be wrong that) implementing conditionals, looping, and user interaction in Bash isn't fun. I wish I could do it in a language like JavaScript, Lisp, Rust, or similar, those being the languages I'm more familiar with. I've also had a couple of projects at my GitHub where I've executed shell scripts from Node and Rust. This makes me wonder how simple could it be to handle most of the complex logic including user I/O in such a programming/scripting language while spawning non-interacting bash shells when needed, instead of limiting myself (especially with my limited knowledge and familiarity with Bash)...

You need to ensure that you have write access to the directory in which you clone a repository. I do have access, I could create directories and files, and I even ran an instance of Syncthing, synced a "folder" with another computer running Syncthing. It's just that git was having trouble. Following is what I see on the console: bash-5.1# git clone https://github.com/myTerminal/twiner.git Cloning into 'twiner'... remote: Enumerating objects: 450, done. error: unable to get random bytes for temporary file: No such file or directory error: unable to get random bytes for temporary file: No such file or directory fatal: Unable to create temporary file '/var/twiner/.git/objects/pack/tmp_pack_XXXXXX': No such file or directory remote: Counting objects: 100% (22/22), done. remote: Compressing objects: 100% (18/18), done. fatal: fetch-pack: invalid index-pack output

Getting to know Linux better from my initial days with beginner-friendly distributions to stepping into the manual installation of Arch (pacstrap), Debian (debootstrap), and Void (xbps) has taught me a lot more of Bash than I would have expected from myself. I now also maintain my personalized setup scripts along with my dotfiles. Furthermore, I also created twiner as a re-usable tool (that tries to be a lot of things at the same time), which "sort of" helped me deepen my understanding of Bash a little bit more.

Now that we have a running Linux system, we can bring in my custom setup scripts and set up the rest of the system with a little help from twiner.

I never had a proper introduction to shell scripting before and as far as I remember, my first shell script was indeed the simple packages installation script for my Linux setup. Needless to say, I started improving my setup scripts and soon realized that most of the scripts that I was writing could be re-used. Around the same time, due to my failure of being able to run a regular Linux distribution on my Dell Precision T3600 desktop due to the incompatibility of the super-old hardware with the latest Xserver packages, I literally had to learn setting up a command-line Linux for graphical use. More configuration meant adding more code to my setup scripts, and all this extra code was a perfect candidate for my library of functions for Linux setup and this led me to create twiner.