From 0287418bfc617547ab88453f0b6ef9fe1d779acd Mon Sep 17 00:00:00 2001 From: Dylan Bolger Date: Thu, 9 Nov 2023 22:22:02 -0600 Subject: update readme for 2023 --- README | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/README b/README index c438ed9..6b0d330 100644 --- a/README +++ b/README @@ -1,7 +1,8 @@ dots dotfiles to infect computers with +mwwuahahahahahahahahahahahahahaha --------------------------------- -Dylan Bolger 2022 +Dylan Bolger 2023 --------------------------------- this project manages my dotfiles. the goal is system-agnostic on any UNIX distro @@ -14,13 +15,12 @@ how this works: * git add -f "fileName" from the home dir when I want to add a file here * to manage different wms/setups, i'll be using branches - here's the idea: - - master => general purpose configuration, useful for any UNIX system I lay my hands on + - dotworld => the new land of the dots for any distro - sway => branch specific to my sway configuration, will have all changes from master that don't conflict - - awesomewm => branch specific to my awesomewm configuration, will have all changes from master that don't conflict - - this way, if I don't want my sway configs lingering around the fs, I can pull the branch which has the - general purpose stuff combined with sway (the sway branch) and I'll have sway + everything I need +* configuration for a specific device. since I use these dots at work, I don't want to have my personal Git intermingle with my work Git user + - .env is a template for defining a specific environment setup + - load_dots is the bread and butter for loading things in feel free to take inspiration from this layout of dotfiles, etc. however, forking dotfiles is NOT a good idea. you should always build out your own dots and customize them to your extent. - -- cgit v1.2.3