Description

Programs and scripts written in POSIX shell and BASH.

As of 2023-06-03, here are some highlights:

• autoexec - Development tool for automatic execution of files
• backmeup - Simple and portable solution to HOME backup
• cito - Portable installer for local or GitHub files
• csi3 - Command-line cheat sheet for i3-wm/i3-gaps
• glkfu - Automate compilation of stable kernels for Ubuntu systems
• lmc-darklight - Scheduled dark/light themes for Linux Mint Cinnamon
• rmne - Remove all of the non-essential Debian packages
• simplify-ubuntu - De-bloat Ubuntu by interactively removing unneeded packages
• tagged - List commits per file in the CWD of a git(1) repository

As of 2023-08-18, here are some other useful tools:

• baddot - Scan directories for filenames containing suspicious 'dot' Unicode
• deb-chklist - Scan '*.list' files for errors.
• fsit - Do nothing until the given file is touched
• recents - List recently opened files in traditional desktop environments
• roks - Clean the system out of old Linux kernel installations
• snotes - View and filter notes from a predefined programming notes file
• wgodw - Present list of recent highlights from DistroWatch

As of 2023-06-18, here are some of the more educational highlights:

• fibdemo - Demonstration of recursive functions for the Fibonacci sequence
• lsdesktops - POSIX shell script for listing '*.desktop' files
• lspath - POSIX shell script for listing $PATH executable files
• pbtree - Pure BASH tool for recursively listing directory trees
• pkgstats - Gather, store, and maintain list of available packages and their file sizes.
• posix-recurse - Isolated example of recursing through directories using a POSIX shell

Contributions

The best way to help is to let me know of any bugs or oversights.

If you wish to contribute any code, try to keep to the existing programming style. Avoid reaching outside of the language whenever possible or reasonable, and keep things consistent and presentable. If you're contributing a new file, such as a helper or wrapper, try to stick to similar dependencies (where reasonable) and please keep the style of the output the same.

If submitting any documentation, try to ensure the English is correct and presentable.