james/dotfiles
1
0
Fork 0
Code Issues 7 Pull Requests Releases Activity
239 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%
59a8c7a6a2
Go to file
James Patrick 59a8c7a6a2 Temp switch to chruby. 
rbenv, et al are having issues with Arch and ruby. I'm not sure where
the source of the issue is but I've tried a couple of different install
paths for both ruby and the version management tools. They all seem to
be having about the same issue.
2020-03-08 17:57:18 -04:00
emacs Updating to match current doom configuration sample 2020-03-08 17:54:05 -04: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 Update print to match current XDG setup. 2020-01-11 00:41:39 -05:00
tmux Cleaned up makefile 2019-12-15 01:37:19 -05:00
tridactyl Added scrolling to tridactyl theme. 2020-03-02 10:26:28 -05:00
vim Removed unused or underused plugins for vim. 2020-01-28 13:45:44 -05:00
waybar Removed the silent @ as recipe echoing is disabled. 2019-12-13 12:00:11 -05:00
zsh Temp switch to chruby. 2020-03-08 17:57:18 -04:00
.gitignore Added support for both DOOM and Spacemacs 2019-08-04 20:41:05 -04:00
makefile Simplified base level make to recursive make command. 2019-04-27 18:15:45 -04:00
README.md Updated readme for project 2019-12-04 01:01:09 -05: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.