diff --git a/.doom.d/.projectile b/.doom.d/.projectile
deleted file mode 100644
index e69de29b..00000000
diff --git a/.doom.d/config.el b/.doom.d/config.el
deleted file mode 100644
index 71f21fba..00000000
--- a/.doom.d/config.el
+++ /dev/null
@@ -1,250 +0,0 @@
-;;; $DOOMDIR/config.el -*- lexical-binding: t; -*-
-
-;; DO NOT EDIT THIS FILE DIRECTLY
-;; This is a file generated from a literate programing source file located at
-;; https://github.com/starr-dusT/dotfiles/blob/master/.doom.d/doomed.org
-;; You should make any changes there and regenerate it from Emacs org-mode
-;; using org-babel-tangle (C-c C-v t)
-
-;; Place your private configuration here! Remember, you do not need to run 'doom
-;; sync' after modifying this file!
-
-;; Some functionality uses this to identify you, e.g. GPG configuration, email
-;; clients, file templates and snippets.
-;; (setq user-full-name "John Doe"
-;; user-mail-address "john@doe.com")
-
-;; Doom exposes five (optional) variables for controlling fonts in Doom. Here
-;; are the three important ones:
-;;
-;; + `doom-font'
-;; + `doom-variable-pitch-font'
-;; + `doom-big-font' -- used for `doom-big-font-mode'; use this for
-;; presentations or streaming.
-;;
-;; They all accept either a font-spec, font string ("Input Mono-12"), or xlfd
-;; font string. You generally only need these two:
-;; (setq doom-font (font-spec :family "monospace" :size 12 :weight 'semi-light)
-;; doom-variable-pitch-font (font-spec :family "sans" :size 13))
-
-;; There are two ways to load a theme. Both assume the theme is installed and
-;; available. You can either set `doom-theme' or manually load a theme with the
-;; `load-theme' function. This is the default:
-;; (setq doom-theme 'doom-one)
-
-;; If you use `org' and don't want your org files in the default location below,
-;; change `org-directory'. It must be set before org loads!
-;; (setq org-directory "~/org/")
-
-;; This determines the style of line numbers in effect. If set to `nil', line
-;; numbers are disabled. For relative line numbers, set this to `relative'.
-;; (setq display-line-numbers-type t)
-
-;; Here are some additional functions/macros that could help you configure Doom:
-;;
-;; - `load!' for loading external *.el files relative to this one
-;; - `use-package!' for configuring packages
-;; - `after!' for running code after a package has loaded
-;; - `add-load-path!' for adding directories to the `load-path', relative to
-;; this file. Emacs searches the `load-path' when you load packages with
-;; `require' or `use-package'.
-;; - `map!' for binding new keys
-;;
-;; To get information about any of these functions/macros, move the cursor over
-;; the highlighted symbol at press 'K' (non-evil users must press 'C-c c k').
-;; This will open documentation for it, including demos of how they are used.
-;;
-;; You can also try 'gd' (or 'C-c c d') to jump to their definition and see how
-;; they are implemented.
-
-(setq this-system "kestrel")
-(setq system-category-1 '("kestrel" "basilisk" "adjudicator"))
-(setq system-category-2 '("kestrel"))
-
-(setq user-full-name "Tyler Starr"
- user-mail-address "starrtyler88@gmail.com")
-
-;; Doom exposes five (optional) variables for controlling fonts in Doom. Here
-;; are the three important ones:
-;;
-;; + `doom-font'
-;; + `doom-variable-pitch-font'
-;; + `doom-big-font' -- used for `doom-big-font-mode'; use this for
-;; presentations or streaming.
-;;
-;; They all accept either a font-spec, font string ("Input Mono-12"), or xlfd
-;; font string. You generally only need these two:
-;; (setq doom-font (font-spec :family "monospace" :size 12 :weight 'semi-light)
-;; doom-variable-pitch-font (font-spec :family "sans" :size 13))
-;; There are two ways to load a theme. Both assume the theme is installed and
-;; available. You can either set `doom-theme' or manually load a theme with the
-;; `load-theme' function. This is the default:
-(setq doom-theme 'doom-dracula)
-
-;; This determines the style of line numbers in effect. If set to `nil', line
-;; numbers are disabled. For relative line numbers, set this to `relative'.
-(setq display-line-numbers-type 'relative)
-
-(map! :leader
- ; Add to the "open" menu in Doom
- (:prefix-map ("o" . "open")
- (:prefix-map ("o" . "org-ql")
- :desc "views" "v" #'org-ql-view
- :desc "Weekly Agenda" "w" (cmd! (org-ql-view "Weekly Agenda"))
- :desc "Tasks to Refile" "r" (cmd! (org-ql-view "Tasks to Refile"))
- :desc "This Weeks Progress" "p" (cmd! (org-ql-view "This Weeks Progress")))))
-
-(setq org-directory "~/documents/org/")
-(setq org-capture (directory-files-recursively
- (concat org-directory "gtd/capture/") "\.org$"))
-(setq org-agenda (directory-files-recursively
- (concat org-directory "gtd/agenda/") "\.org$"))
-(setq org-todo (directory-files-recursively
- (concat org-directory "gtd/todo/") "\.org$"))
-(setq org-agenda-files (append org-capture org-agenda org-todo))
-
-(setq org-roam-directory (concat org-directory "roam"))
-(setq org-roam-db-location (concat org-directory "roam/org-roam.db"))
-
-(after! org
- (setq org-todo-keywords
- (quote ((sequence "TODO(t)" "NEXT(n)" "|" "DONE(d)")
- (sequence "WAITING(w@/!)" "HOLD(h@/!)" "|"
- "CANCELLED(c@/!)"))))
- ; TODO add (1)...(10) numbers for task ordering (replacing "next")
- (setq org-todo-keyword-faces
- (quote (("TODO" :foreground "red" :weight bold)
- ("CHASE" :foreground "red" :weight bold)
- ("WIP" :foreground "blue" :weight bold)
- ("GAVE" :foreground "orange" :weight bold)
- ("KILL" :foreground "forest green" :weight bold)
- ("DONE" :foreground "forest green" :weight bold))))
-
- (setq org-use-tag-inheritance t)
- (setq org-tags-exclude-from-inheritance '("prj" "prg" "subprj"))
- (setq org-tag-alist
- '((:startgroup)
- ; Put mutually exclusive tags here
- (:endgroup)
- ("@home" . ?h)
- ("@work" . ?w)
- ("question" . ?q)
- ("prj" . ?p)
- ("subprj" . ?s)
- ("prg" . ?P)
- ("habit" . ?h)
- ("me" . ?m)
- ("Aaron" . ?a)
- ("Landon" . ?l)
- ("Valerie" . ?v)
- ("David" . ?d)))
-
- (setq org-capture-todo (concat org-directory "gtd/capture/inbox.org"))
-
- (setq org-capture-templates
- (doct '(("todo" :keys "t"
- :file org-capture-todo
- :template ("* TODO %?" "%U"))
- ("question" :keys "q"
- :file org-capture-todo
- :template ("* TODO Find out %? :question:@home:"
- "%U"))
- ("habit" :keys "h"
- :file org-capture-todo
- :template ("* NEXT %? :habit" "%U"
- "SCHEDULED: %(format-time-string
- \"%<<%Y-%m-%d %a .+1d/3d>>\")"
- ":PROPERTIES:" ":STYLE: habit"
- ":REPEAT_TO_STATE: NEXT" ":END:"))
- ("meeting" :keys "m"
- :file org-capture-todo
- :template ("* NEXT %? :meeting:"
- "%U")))))
-
- (setq org-refile-targets (quote ((nil :maxlevel . 3)
- (org-agenda-files :maxlevel . 3))))
- (advice-add 'org-refile :after 'org-save-all-org-buffers)
-
- (setq org-agenda-start-day "0d")
- (setq org-agenda-custom-commands
- '(("t" "Agenda for today" agenda ""
- ((org-agenda-overriding-header "Today's agenda")
- (org-agenda-span 'day)))))
-
- (setq org-ql-weekly-agenda
- (cons "Weekly Agenda"
- (lambda ()
- "Open agenda for week."
- (interactive)
- (org-agenda nil "t"))))
-
- (setq org-ql-refile-tasks
- (cons "Tasks to Refile"
- (lambda ()
- "Find tasks to refile."
- (interactive)
- (org-ql-search (list org-capture-todo)
- '(or (not (done))
- (done))
- :title "Tasks to Refile"
- :sort '(date priority todo)
- :super-groups '((:name "Todos"
- :not (:tag "note")))))))
-
- (setq org-ql-weeks-progress
- (cons "This Weeks Progress"
- (lambda ()
- "launch an agenda-like view at the specified date."
- (interactive)
- (let* ((ts (ts-now))
- (beg-of-week (->> ts
- (ts-adjust 'day (- (ts-dow (ts-now))))
- (ts-apply :hour 0 :minute 0 :second 0)))
- (end-of-week (->> ts
- (ts-adjust 'day (- 6 (ts-dow (ts-now))))
- (ts-apply :hour 23 :minute 59 :second 59))))
- (org-ql-search (org-agenda-files)
- '(ts-active :from beg-of-week :to end-of-week)
- :title "Week Overview"
- :sort '(date priority todo)
- :super-groups '((:name "Late"
- :scheduled past
- :deadline past)
- (:name "Today"
- :time-grid t
- :scheduled today
- :deadline today)
- (:name "Coming Up"
- :scheduled future
- :deadline future)))))))
-
- (defun open-org-ql-project (program)
- (org-ql-search (list program)
- '(and (todo)
- (ancestors (todo))))
- :super-groups '((:auto-outline-path t)))
-
- (setq org-ql-project-view
- (cons "Project View"
- (lambda ()
- "launch a project view for a given program."
- (interactive)
- (ivy-read "Project: "
- (org-agenda-files)
- :require-match t
- :action #'open-org-ql-project))))
-
- (setq org-super-agenda-header-map (make-sparse-keymap))
- (setq org-ql-views
- (list org-ql-weekly-agenda
- org-ql-refile-tasks
- org-ql-weeks-progress
- org-ql-project-view))
- (after! org-agenda
- (org-super-agenda-mode))
-
- (setq org-startup-folded t)
- (setq org-src-preserve-indentation t)) ; Close the after! org expression from
- ; Org File Paths
-
-(add-hook 'haskell-mode-hook #'hindent-mode)
diff --git a/.doom.d/custom.el b/.doom.d/custom.el
deleted file mode 100644
index 71a498ff..00000000
--- a/.doom.d/custom.el
+++ /dev/null
@@ -1 +0,0 @@
-(put 'upcase-region 'disabled nil)
diff --git a/.doom.d/doomed.org b/.doom.d/doomed.org
deleted file mode 100644
index 837814f5..00000000
--- a/.doom.d/doomed.org
+++ /dev/null
@@ -1,648 +0,0 @@
-#+title: Doomed - Personal Doom Emacs Config
-#+author: Tyler Starr
-#+email: tyler@tstarr.us
-#+keywords: org-mode Emacs Doom config
-* References
-
-Configuring Emacs can be an obsession. I have bounced back and forth between my from [[https://github.com/starr-dusT/scratch][scratch]] config and doom. In the end I find it hard to give up all the amazing work [[https://github.com/hlissner][hlissner]] has put into doom. Doom really simpifies the process of configuring Emacs with lots of pre-made bits and a nice framework for configuration. As much as it annoys me to not completelty control the config of the whole system I must comprimise to maintain my sanity. Find some useful references below:
-
-- [[https://github.com/hlissner/doom-emacs][Doom Emacs Github]]
-- [[https://github.com/zzamboni/dot-doom][zzamboni's nice config]]
-
-* Doom config file overview
-
-Doom Emacs uses three config files:
-
-- =init.el= defines which of the existing Doom [[https://github.com/hlissner/doom-emacs/blob/develop/docs/getting_started.org#modules][modules]] are loaded. A Doom module is a bundle of packages, configuration and commands, organized into a unit that can be toggled easily from this file.
-- =packages.el= defines which [[https://github.com/hlissner/doom-emacs/blob/develop/docs/getting_started.org#package-management][packages]] should be installed, beyond those that are installed and loaded as part of the enabled modules.
-- =config.el= contains all [[https://github.com/hlissner/doom-emacs/blob/develop/docs/getting_started.org#configuring-doom][custom configuration]] and code.
-
-There are other files that can be loaded, but theses are the main ones. The load order of different files is [[https://github.com/hlissner/doom-emacs/blob/develop/docs/getting_started.org#load-order][defined depending on the type of session]] being started.
-
-All the config files are generated from this Org file, to try and make its meaning as clear as possible. All =package!= declarations are written to =packages.el=, all other LISP code is written to =config.el=.
-
-** Config file headers
-
-We start by simply defining the standard headers used by the three files. These headers come from the initial files generated by =doom install=, and contain either some Emacs-LISP relevant indicators like =lexical-binding=, or instructions about the contents of the file.
-
-#+html: init.el
-#+begin_src emacs-lisp :tangle init.el
-;;; init.el -*- lexical-binding: t; -*-
-
-;; DO NOT EDIT THIS FILE DIRECTLY
-;; This is a file generated from a literate programing source file located at
-;; https://github.com/starr-dusT/dotfiles/blob/master/.doom.d/doomed.org
-;; You should make any changes there and regenerate it from Emacs org-mode
-;; using org-babel-tangle (C-c C-v t)
-
-;; This file controls what Doom modules are enabled and what order they load
-;; in. Remember to run 'doom sync' after modifying it!
-
-;; NOTE Press 'SPC h d h' (or 'C-h d h' for non-vim users) to access Doom's
-;; documentation. There you'll find a "Module Index" link where you'll find
-;; a comprehensive list of Doom's modules and what flags they support.
-
-;; NOTE Move your cursor over a module's name (or its flags) and press 'K' (or
-;; 'C-c c k' for non-vim users) to view its documentation. This works on
-;; flags as well (those symbols that start with a plus).
-;;
-;; Alternatively, press 'gd' (or 'C-c c d') on a module to browse its
-;; directory (for easy access to its source code).
-#+end_src
-
-#+RESULTS:
-
-#+html: packages.el
-#+begin_src emacs-lisp :tangle packages.el
-;; -*- no-byte-compile: t; -*-
-;;; $DOOMDIR/packages.el
-
-;; DO NOT EDIT THIS FILE DIRECTLY
-;; This is a file generated from a literate programing source file located at
-;; https://github.com/starr-dusT/dotfiles/blob/master/.doom.d/doomed.org
-;; You should make any changes there and regenerate it from Emacs org-mode
-;; using org-babel-tangle (C-c C-v t)
-
-;; To install a package with Doom you must declare them here and run 'doom sync'
-;; on the command line, then restart Emacs for the changes to take effect -- or
-;; use 'M-x doom/reload'.
-
-;; To install SOME-PACKAGE from MELPA, ELPA or emacsmirror:
-;;(package! some-package)
-
-;; To install a package directly from a remote git repo, you must specify a
-;; `:recipe'. You'll find documentation on what `:recipe' accepts here:
-;; https://github.com/raxod502/straight.el#the-recipe-format
-;;(package! another-package
-;; :recipe (:host github :repo "username/repo"))
-
-;; If the package you are trying to install does not contain a PACKAGENAME.el
-;; file, or is located in a subdirectory of the repo, you'll need to specify
-;; `:files' in the `:recipe':
-;;(package! this-package
-;; :recipe (:host github :repo "username/repo"
-;; :files ("some-file.el" "src/lisp/*.el")))
-
-;; If you'd like to disable a package included with Doom, you can do so here
-;; with the `:disable' property:
-;;(package! builtin-package :disable t)
-
-;; You can override the recipe of a built in package without having to specify
-;; all the properties for `:recipe'. These will inherit the rest of its recipe
-;; from Doom or MELPA/ELPA/Emacsmirror:
-;;(package! builtin-package :recipe (:nonrecursive t))
-;;(package! builtin-package-2 :recipe (:repo "myfork/package"))
-
-;; Specify a `:branch' to install a package from a particular branch or tag.
-;; This is required for some packages whose default branch isn't 'master' (which
-;; our package manager can't deal with; see raxod502/straight.el#279)
-;;(package! builtin-package :recipe (:branch "develop"))
-
-;; Use `:pin' to specify a particular commit to install.
-;;(package! builtin-package :pin "1a2b3c4d5e")
-
-;; Doom's packages are pinned to a specific commit and updated from release to
-;; release. The `unpin!' macro allows you to unpin single packages...
-;;(unpin! pinned-package)
-;; ...or multiple packages
-;;(unpin! pinned-package another-pinned-package)
-;; ...Or *all* packages (NOT RECOMMENDED; will likely break things)
-;;(unpin! t)
-#+end_src
-#+html: config.el
-#+begin_src emacs-lisp :tangle config.el
-;;; $DOOMDIR/config.el -*- lexical-binding: t; -*-
-
-;; DO NOT EDIT THIS FILE DIRECTLY
-;; This is a file generated from a literate programing source file located at
-;; https://github.com/starr-dusT/dotfiles/blob/master/.doom.d/doomed.org
-;; You should make any changes there and regenerate it from Emacs org-mode
-;; using org-babel-tangle (C-c C-v t)
-
-;; Place your private configuration here! Remember, you do not need to run 'doom
-;; sync' after modifying this file!
-
-;; Some functionality uses this to identify you, e.g. GPG configuration, email
-;; clients, file templates and snippets.
-;; (setq user-full-name "John Doe"
-;; user-mail-address "john@doe.com")
-
-;; Doom exposes five (optional) variables for controlling fonts in Doom. Here
-;; are the three important ones:
-;;
-;; + `doom-font'
-;; + `doom-variable-pitch-font'
-;; + `doom-big-font' -- used for `doom-big-font-mode'; use this for
-;; presentations or streaming.
-;;
-;; They all accept either a font-spec, font string ("Input Mono-12"), or xlfd
-;; font string. You generally only need these two:
-;; (setq doom-font (font-spec :family "monospace" :size 12 :weight 'semi-light)
-;; doom-variable-pitch-font (font-spec :family "sans" :size 13))
-
-;; There are two ways to load a theme. Both assume the theme is installed and
-;; available. You can either set `doom-theme' or manually load a theme with the
-;; `load-theme' function. This is the default:
-;; (setq doom-theme 'doom-one)
-
-;; If you use `org' and don't want your org files in the default location below,
-;; change `org-directory'. It must be set before org loads!
-;; (setq org-directory "~/org/")
-
-;; This determines the style of line numbers in effect. If set to `nil', line
-;; numbers are disabled. For relative line numbers, set this to `relative'.
-;; (setq display-line-numbers-type t)
-
-;; Here are some additional functions/macros that could help you configure Doom:
-;;
-;; - `load!' for loading external *.el files relative to this one
-;; - `use-package!' for configuring packages
-;; - `after!' for running code after a package has loaded
-;; - `add-load-path!' for adding directories to the `load-path', relative to
-;; this file. Emacs searches the `load-path' when you load packages with
-;; `require' or `use-package'.
-;; - `map!' for binding new keys
-;;
-;; To get information about any of these functions/macros, move the cursor over
-;; the highlighted symbol at press 'K' (non-evil users must press 'C-c c k').
-;; This will open documentation for it, including demos of how they are used.
-;;
-;; You can also try 'gd' (or 'C-c c d') to jump to their definition and see how
-;; they are implemented.
-#+end_src
-#+html: