jpm
/
.dotfiles
1
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity
291 Commits 2 Branches 0 Tags 88 MiB
CSS 91.3%
Shell 8.6%
Go to file
John Mertz a8920ad9b7 Freshen up that prompt! 
Emulate a Powerline setup. Includes:
* Change custom foreground colours to background colours
* Add 8 different separators, selected randomly based on terminal ID
* Prettier and more sensible Git repo sigils
* Cleaned and condensed code
 		2024-08-16 22:26:07 -06:00
alacritty Add B+W config for eInk display 2024-08-16 21:06:29 -06:00
bash Freshen up that prompt! 2024-08-16 22:26:07 -06:00
fastfetch toolbox->fedora 2024-01-31 21:57:14 -07:00
fonts
…
gtk
…
icons
…
neofetch
…
rofi
…
sway Update app_id's 2024-07-22 21:04:27 -06:00
swaylock Custom Swaylock theme 2024-02-22 22:53:09 -07:00
systemd Update state file path 2024-06-19 16:48:17 -06:00
themes/Gruvbox
…
tofi Better spacing around selection 2024-03-08 13:54:38 -07:00
vim
…
waybar Move .spool to XDG state directory 2024-03-08 14:23:54 -07:00
wofi
…
xfce4/terminal
…
yazi Start using yazi file manager 2024-02-08 16:49:17 -07:00
zathura Initial Zathura config. Recolor to light on dark. 2024-03-08 12:50:26 -07:00
.gitignore
…
README.md Move .spool to XDG state directory 2024-03-08 14:23:54 -07:00
mako.conf Hide mode for mako 2024-04-19 18:02:34 -06:00
symlink.sh
…

README.md

${HOME}/.dotfiles

Version control for dotfiles and templates.

Purpose

${HOME}/.config and ${HOME} are a nightmare to version control. Maintaining a distinct dotfile directory then linking to those files is a much more sane way to cordon them off from the rest of the mess.

Usage

Make changes and maintain dotfiles in this directory.

TODO: Everything below Define symlinks or dumper within the .links file.

Run ${HOME}/scripts/update_configs.pl to refresh links and dump templates.

Details

.links

This file contains a JSON hash of the configuration files available with either a path to be linked, or the name of a dumper contained within ${HOME}/scripts/dotfiles.

${HOME}/.local/state/dotfiles.json

This file contains a JSON hash of timestamps at which each configuration was last linked or dumped. The ${HOME}/scripts/update_configs.pl script will use these times to know whether or not they need to be updated. It will do so if:

  • it is a linked configuration file and the .links file has been updated since it was last linked.
  • it is a dumpable template and the template has been updated since the last logged event.