1
Fork 0
My config files for various things
  • Shell 78.7%
  • JavaScript 19.7%
  • Batchfile 1.6%
Find a file
2025-12-20 08:16:02 -05:00
bash bash: remove nodejs_ipv4.profile 2025-09-13 18:11:51 -04:00
firefox firefox: keepassxc-browser: disable save credentials prompt banner 2025-11-24 15:56:28 -05:00
gcloud rework symlinking and locations of several files 2021-11-13 17:06:05 -05:00
git git: add development as a lazygit main branch 2025-12-11 15:09:40 -05:00
keepassxc keepassxc: remove global autotype key; don't minimize on startup 2025-12-20 08:16:02 -05:00
nodejs nodejs: getnodejs.sh: install corepack if not automatically installed 2025-10-29 05:44:29 -04:00
tmux use long form of command line options where possible 2021-02-09 20:59:02 -05:00
vscode vscode: acf.im -> acf.sh 2025-09-04 21:20:22 -04:00
win win: add disable_sbat_updates.reg 2024-11-02 08:52:11 -04:00
wsl wsl: make creating new user optional 2025-01-02 11:05:14 -05:00
config.sh git: add lazygit with initial configuration 2025-12-11 04:26:52 -05:00
README.md keepassxc: add initial version of config 2025-11-01 02:00:58 -04:00

config

My config files for various things. See the individual readmes below.

Use config.sh to automate the setup of a number of things.

For simplicity, the config.sh script uses ln --relative --symbolic even for creating links that are between two Windows paths. In order for this to result in working Windows symbolic links, Windows must be in developer mode and this repository must be cloned to the Windows filesystem on the drive containing your user profile. There is a registry script to enable developer mode here, which lets Windows create symbolic links without privilege escalation. And when this repository lives on the same drive as the user profile, the relative path between two paths under WSL's (say) /mnt/c/... will be the same as the relative path between the two corresponding paths under C:\....