synle/bashrc

Personal bash profile and dotfiles management system. Automates shell configuration, editor settings, fonts, Git config, and OS-specific tweaks across 6+ platforms from a single codebase.

Demo

https://synle.github.io/bashrc/

Supported Platforms

• macOS
• Ubuntu / Debian / Mint
• Windows (PowerShell + MinGW) / WSL
• Android Termux
• Arch Linux / SteamOS
• ChromeOS
• Red Hat / Fedora

Highlights

Cross-Platform Tab Completion System (Complete-Spec)

A custom spec-based autocomplete system that works on both Bash and PowerShell from the same source files. Plain text spec files define completions for any command -- no shell-specific syntax required.

• 37 spec files covering 48 commands (including aliases like g for git, n for npm)
• 27 dynamic tokens that expand at tab time (__git_branches__, __npm_scripts__, __makefile_targets__, __ssh_hosts__, etc.)
• Nested subcommand support (kubectl rollout status <TAB> gives resource types + flags)
• Spec generators that auto-build specs from --help output (git, docker, npm)
• Alias proxying -- one line to give any alias the same completions as its target command

Spec format -- one line per subcommand, one file per command:

checkout|__git_branches__,__git_files__,--force,-f,-b,-B,--track,-t
commit|__git_commit_flags__
push|__git_remotes__,__git_branches__,--force,-f,--set-upstream,-u
run|__npm_scripts__

Marker-Based Profile Assembly

~/.bash_syle is assembled from 20+ self-contained scripts using # BEGIN/# END markers. Each script owns its own section -- add a tool by creating one file, remove it by deleting that file. No central config to edit.

Node | Bash Pipeline

Scripts are written in Node.js but execute as bash. cat index.js | node | bash -- Node generates bash commands to stdout, bash executes them. This gives you the full power of Node (async I/O, JSON parsing, template literals) with native shell integration.

Tagged Template Literal API

Six tagged template literals replace a dozen legacy functions with one consistent pattern:

code`...`; // dedented string
list`...`; // array of lines
json`{ "key": "value" }`; // parsed JSONC
await readText`software/scripts/foo.bash`; // universal reader (file, URL, or repo path)
await readJson`software/scripts/foo.jsonc`; // universal JSONC reader

Build-Include System

A marker-based build system that inlines file content between # BEGIN path / # END path markers and processes // {{theme.key}} inline markers in JSONC files from a central color map. One make format_build_include keeps everything in sync.

Editor Configuration

Manages settings, keybindings, extensions, and themes for VS Code, Sublime Text, Zed, and Vim across all platforms. Dark/light theme colors are centralized in one color map and propagated to all editor configs at build time.

CI/CD

GitHub Actions with 5 parallel OS builds (Ubuntu, RHEL, Arch, Debian, macOS), automated formatting, webapp deployment to GitHub Pages, and profile syntax testing across all platforms.

Installation

if [ "$(echo "${SKIP_SETUP:-}" | tr -d '[:space:]')" = "true" ] || [ "$(echo "${SKIP_SETUP:-}" | tr -d '[:space:]')" = "1" ]; then
  echo ">> SKIP_SETUP is set, skipping dependency setup"
  curl -fsSL https://raw.githubusercontent.com/synle/bashrc/master/run.sh | bash -s -- --prod
else
  curl -fsSL https://raw.githubusercontent.com/synle/bashrc/master/run.sh | bash -s -- --prod --setup
fi

Usage

make setup_local       # Bootstrap from local files
make setup_prod        # Bootstrap from GitHub
make validate          # Format + run tests
make build             # Build all artifacts
make test_all          # Run all test suites
make clean             # Clean up
make doctor            # Run diagnostics

run.sh

bash run.sh                          # Full local run
bash run.sh --prod                   # Full run from GitHub
bash run.sh --files="git.js"         # Run specific file(s)
bash run.sh git.js vim-config.js     # Bare args as files
bash run.sh --debug                  # Keep temp files, show retry commands
bash run.sh --force-refresh          # Reinstall stale dependencies
bash run.sh --dryrun                 # Show what would change without writing
bash run.sh --remove --files="fzf.js"  # Remove a script's config

Architecture

run.sh / Makefile
  -> source common-env.sh (OS detection, env vars)
  -> cat software/index.js | node | bash
       -> index.js discovers scripts, emits bash commands to stdout
       -> bash executes them (installs tools, writes configs, assembles profile)
  -> ~cleanup.js strips unfilled markers, writes build artifacts

Scripts are auto-discovered from software/scripts/. Filename prefixes control execution order (_init first, ~cleanup last, alphabetical in between). OS-specific scripts live in software/scripts/<os>/.

Fun Facts

Current Equipment

Legion Go Deck

Upgraded to 2TB 2280 NVMe with an adapter. Installed SteamOS.

Laptop (Asus ROG G14)

• AMD 7940S
• GeForce 4060
• Upgraded to 40GB RAM
• Upgraded to 2TB NVMe
• Dual boot Windows 11 IoT LTSC (with WSL 2 / Ubuntu 24.04) / Linux Mint

AI Workstation (HP Omen 45L)

• Intel Core Ultra 9 285K
• 64GB Kingston FURY DDR5-5600
• NVIDIA GeForce RTX 5090 (32GB GDDR7)
• Dual boot Windows 11 IoT LTSC (with WSL 2 / Ubuntu 24.04) / Linux Mint

Past Equipments

Steam Deck

Upgraded from 64GB eMMC to 1TB 2230 NVMe.

Laptop (Gigabyte Aero 16)

• Intel Core i7-12700H
• GeForce 3070 Ti
• Upgraded to 64GB RAM, 2TB NVMe
• Windows 10 IoT LTSC (with WSL 2 / Debian)

macOS Laptop (MacBook Pro 14" M1 - 16GB / 512GB)

Chromebook (Samsung - 8GB / 128GB)

• ChromeOS with Ubuntu container

Desktop (Lenovo P520)

• Intel Xeon W-2145
• Upgraded to 128GB RAM
• 2x2TB NVMe, 8TB HDD
• Gigabyte Eagle 3090
• Custom fan mods (2x120mm intake, 120mm exhaust)
• Dual boot Windows 10 IoT LTSC / Ubuntu 22.04