All CustomRC configuration is managed in ~/.customrc/configs.sh.
CustomRC supports two modes controlled by CUSTOMRC_DEBUG_MODE.
Enable verbose output with per-module timing by setting CUSTOMRC_DEBUG_MODE=true:
[i] Initializing Customrc...
━━━━[customrc]━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✓ Loaded: fzf.sh [Global] (3ms)
✓ Loaded: bat.sh [Global] (1ms)
✗ Ignored: nvm.sh [Global]
✓ Loaded: brew.sh [Darwin] (2ms)
━━━━[customrc]━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[i] Initialization complete
✓ Loaded: 24
✗ Ignored: 5
⚠ Duration: 89ms
Use debug mode when:
- Developing new modules
- Troubleshooting slow startup times
- Identifying which modules are being loaded
When CUSTOMRC_DEBUG_MODE=false (default), CustomRC generates a monolithic cache file combining all modules. This cache:
- Auto-regenerates when any module or
configs.shchanges - Sources instantly without per-file overhead
- Lives at
~/.cache/customrc/monolithic.sh
Production mode is recommended for daily use.
Disable slow or unused modules by adding them to platform-specific ignore lists:
CUSTOMRC_GLOBAL_IGNORE_LIST=(
"nvm.sh" # 200ms+ - use fnm instead
"thefuck.sh" # 100ms+ - lazy load if needed
)
CUSTOMRC_DARWIN_IGNORE_LIST=(
"iterm.sh" # Not needed if using other terminal
)
CUSTOMRC_LINUX_IGNORE_LIST=()Use the customrc cache CLI commands to manage caches. Run customrc cache status to view current cache information.
Use customrc cache clear to remove all caches, or specify a name to clear a specific one:
# Clear all caches
customrc cache clear
# Clear specific cache
customrc cache clear fzfCaches are stored in ~/.cache/customrc/.
Use the CLI to rebuild the monolithic cache:
customrc cache rebuildThis forces regeneration of the monolithic cache file.