james
/
dotfiles
1
0
Fork 0
Code Issues 7 Pull Requests Releases Activity
217 Commits 1 Branch 0 Tags 45 MiB
Shell 45.8%
Emacs Lisp 18.4%
Makefile 15.2%
Vim script 11.6%
CSS 5.3%
Other 3.7%
Go to file
James Patrick 40d8b3fdf3 Added simple theme for report server. 
Its largely based on jackharrisonsherlock's common prompt, but has some
different namespacing, a deterministic prompt color based on the
hostname, and a few other minor changes.

My plan is to add async git info to this, but this is the MVP for this.
 		2019-12-20 10:09:45 -05:00
emacs +tng and +childframe conflict. Don't use both. 2019-12-16 14:05:24 -05:00
git Adding git. 2019-05-03 19:41:39 -04:00
i3 Organizing i3 config. 2019-08-04 17:09:30 -04:00
lib Cleaned up makefile 2019-12-15 01:37:19 -05:00
mako Making mako makescript more verbose. 2019-06-14 21:01:31 -04:00
rofi Added emacs modeline like feature. 2019-12-11 00:55:57 -05:00
ssh Added second public key. 2019-12-13 16:44:01 -05:00
sway Added emacs modeline like feature. 2019-12-11 00:55:57 -05:00
tmux Cleaned up makefile 2019-12-15 01:37:19 -05:00
tridactyl Added some small UI tweaks for tridactyl theme. 2019-12-16 11:30:09 -05:00
vim Removed the silent @ as recipe echoing is disabled. 2019-12-13 12:00:11 -05:00
waybar Removed the silent @ as recipe echoing is disabled. 2019-12-13 12:00:11 -05:00
zsh Added simple theme for report server. 2019-12-20 10:09:45 -05:00
.gitignore Added support for both DOOM and Spacemacs 2019-08-04 20:41:05 -04:00
README.md Updated readme for project 2019-12-04 01:01:09 -05:00
makefile Simplified base level make to recursive make command. 2019-04-27 18:15:45 -04:00

README.md

Hi. This is James Patrick's current collection of dotfiles. If you found this feel free to steal what ever you want, if you have any questions feel free to contact me.

Tenants

  1. The time invested in configuring tools will probably never be recouped by increased productivity. That isn't a reason not to it.
  2. Don't write what already exist.
  3. Config to have easy setup and tear down, without destroying anything important.
  4. Try to stay lean. More tools begets more maintenance.
    1. The best code is no code.
    2. Its better to have a imperfect tool than to have envs diverge.
    3. Allow for variation between envs.
  5. Any rule can be ignored if it has a non-stupid reason.
  6. Take lots of screenshots.
  7. Don't be a idiot and store large files
  8. Do not tightly couple components.