Paracord dot files framework. Simply fork paracord drop your dot files into the appropriate directory and you are locked and loaded.
Original source: https://github.com/BlackMagicMushroom/paracord
- _bin/
- bin/
- core/
- skel/
- skel.cp/
This directory will be symlinked to $HOME/bin, if one exists this will not happen. You will be informed to update $HOME/bin manually.
Paracord bin directory where paracord executable lives.
Paracord specific functions and files.
All dot files and folders here will be symlinked from $PARACORDDIR/skel/{filename} to $HOME/{filename}.
Dot files and folders should be prefixed with DOT (e.g. DOT.bashrc, DOT.login, DOT.vim) and will be
symlinked from $PARACORDDIR/skel/DOT.{filename} to $HOME/.{filename}
All dot files and folders here will be copied from $PARACORDDIR/skel.cp/{filename} to $HOME/{filename}.
Dot files and folders should be prefixed with DOT (e.g. DOT.bashrc, DOT.login, DOT.vim) and will be
copied from $PARACORDDIR/skel.cp/DOT.{filename} to $HOME/.{filename}
The paracord command currently has two available subcommands:
- configure - Updates your web_install.sh file in your repo & configure your ~/.gitconfig with your info
- help - Displays help dialog
- install - Installs your instance of Paracord
- update - Updates from your repo then executes appropritate commands
- update-path - Updates your .local_env file to include the paracord command to your path
- variables - Displays Paracord variables
The way these .files (dot files) are structured follow the simple idea of generic environment elements that can exist across multiple systems all exist in the appropriate .bash_{X} files (e.g. .bash_env, .bash_aliases, et cetra). System specific .files should live in .local_{X} files (e.g. .local_env, .local_aliases, et cetra).
From the commandline execute the following commands (assumes you have git and curl installed).