These are my shell scripts, other custom commands, configuration files, and more. Nothing here is especially groundbreaking or innovative, but I take pleasure in crafting small, useful, beautiful tools with great love and care and with great attention to detail. I'm sharing these things for the benefit of others, and I sincerely hope others find them useful.
My shell scripts and other custom commands are well-documented, and readers may also be interested in my methods of organization, my Bash configuration, my Neovim configuration, my tmux configuration, and my Git configuration, among other things.
Bash shell scripts that might be useful to others are stored in the bin/general directory. They are written to be as general and as self-contained as possible, so that others can easily use them. Please see the README in that directory for more information.
The .config/bash/init/functions directory contains custom commands which generally cannot be implemented as Bash shell scripts for one reason or another.
Bash functions that might be useful to others are stored in the .../functions/general directory. Like the general Bash scripts, the general functions are written to be as general and as self-contained as possible, so that others can easily use them. Please see the README in that directory for more information.
I'm very pleased with the organization of my Bash functions. I've tried many methods of organizing aliases and functions, but this method, inspired by fish, feels the most natural. No aliases are used. Everything is a function, and every function has its own file.
One weakness with the organization of my Bash configuration is that loading an interactive shell is pretty slow, relative to loading an unconfigured Bash session, taking about 1-2 seconds on my laptop. That poor performance may have something to do with how many files need to be read, although a quick experiment in concatenating the files did not seem to speed things up dramatically. Alternatively, the poor performance may be related to how many functions are loaded. In either case, it's something I could look into in the future. For now, it's not worth the effort. Waiting two seconds for a Bash shell to load is never a meaningful bottleneck for me.
Follow these steps to install all of these files:
- Ensure
sudois installed and your user is able to runsudocommands successfully. - Download the dotfiles-openjck-setup-bootstrap script.
- Make dotfiles-openjck-setup-bootstrap executable.
- Run dotfiles-openjck-setup-bootstrap.
See the shell script documentation for information on how to install and use single shell script.
See the function documentation for information on how to install and use a single Bash function.
To ask questions or discuss these files, please use the Discussions page.