Initial Commit

config.el

@@ -0,0 +1,140 @@
+;;; $DOOMDIR/config.el -*- lexical-binding: 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. It is optional.
+;; (setq user-full-name "John Doe"
+;;       user-mail-address "john@doe.com")
+
+;; Doom exposes five (optional) variables for controlling fonts in Doom:
+;;
+;; - `doom-font' -- the primary font to use
+;; - `doom-variable-pitch-font' -- a non-monospace font (where applicable)
+;; - `doom-big-font' -- used for `doom-big-font-mode'; use this for
+;;   presentations or streaming.
+;; - `doom-symbol-font' -- for symbols
+;; - `doom-serif-font' -- for the `fixed-pitch-serif' face
+;;
+
+(setq doom-font "JetBrainsMonoNL NF")
+
+;; See 'C-h v doom-font' for documentation and more examples of what they
+;; accept. For example:
+;;
+;;(setq doom-font (font-spec :family "Fira Code" :size 12 :weight 'semi-light)
+;;      doom-variable-pitch-font (font-spec :family "Fira Sans" :size 13))
+;;
+;; If you or Emacs can't find your font, use 'M-x describe-font' to look them
+;; up, `M-x eval-region' to execute elisp code, and 'M-x doom/reload-font' to
+;; refresh your font settings. If Emacs still can't find your font, it likely
+;; wasn't installed correctly. Font issues are rarely Doom issues!
+
+;; 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)
+(setq doom-theme 'doom-tokyo-night)
+
+;; 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)
+
+;; 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 "C:/Users/EmmaTurner/OneDrive - Exponential Technology Group, Inc/Documents/Notes/")
+
+;; Whenever you reconfigure a package, make sure to wrap your config in an
+;; `after!' block, otherwise Doom's defaults may override your settings. E.g.
+;;
+;;   (after! PACKAGE
+;;     (setq x y))
+;;
+;; The exceptions to this rule:
+;;
+;;   - Setting file/directory variables (like `org-directory')
+;;   - Setting variables which explicitly tell you to set them before their
+;;     package is loaded (see 'C-h v VARIABLE' to look up their documentation).
+;;   - Setting doom variables (which start with 'doom-' or '+').
+;;
+;; Here are some additional functions/macros that will 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.
+;; Alternatively, use `C-h o' to look up a symbol (functions, variables, faces,
+;; etc).
+;;
+;; You can also try 'gd' (or 'C-c c d') to jump to their definition and see how
+;; they are implemented.
+(after! org
+  (setq org-hide-emphasis-markers t)
+  (setq org-log-done 'time)
+
+  ;; Collect all .org from my Org directory and subdirs
+  (defun load-org-agenda-files-recursively (dir) "Find all directories in DIR."
+       (unless (file-directory-p dir) (error "Not a directory '%s'" dir))
+       (unless (equal (directory-files dir nil org-agenda-file-regexp t) nil)
+        (add-to-list 'org-agenda-files dir)
+       )
+       (dolist (file (directory-files dir nil nil t))
+         (unless (member file '("." ".."))
+           (let ((file (concat dir file "/")))
+             (when (file-directory-p file)
+               (load-org-agenda-files-recursively file)
+             )
+           )
+         )
+       )
+  )
+
+  (load-org-agenda-files-recursively org-directory) ; trailing slash required
+
+  (setq org-refile-targets
+      '((nil :maxlevel . 3)
+        (org-agenda-files :maxlevel . 1)))
+)
+
+;; TODO: Find out what _actually_ needs to be set here
+;; i.e. shouldn't need to set both ispell-dictionary and ispell-local-dictionary
+(after! ispell
+  (setq ispell-dictionary "en_US")
+  (setq ispell-local-dictionary "en_US")
+  (setq ispell-extra-args '("-d" "en_US"))
+  (setq ispell-local-dictionary-alist
+        '(("en_US" "[A-Za-z]" "[^A-Za-z]" "[']" nil nil nil utf-8)))
+  (setq ispell-hunspell-dictionary-alist
+        '(("en_US"
+           "C:/hunspell/en_US.aff"
+           "C:/hunspell/en_US.dic"
+           nil nil nil "utf-8")))
+  ;; This is the default hunspell personal dictionary
+  ;; Hunspell won't create it, and ispell needs this file specified to work
+  (setq ispell-personal-dictionary "~/hunspell_en_US")
+)
+
+;; Windows path
+(when (eq system-type 'windows-nt)
+
+  ;; https://emacs.stackexchange.com/a/29949
+  ;; Make sure Unix tools are in front of `exec-path'
+  ;; (let ((bash (executable-find "bash")))
+  ;;   (when bash
+  ;;     (push (file-name-directory bash) exec-path)))
+  (push "C:/Program Files/Git/usr/bin/" exec-path)
+
+  ;; Update PATH from exec-path
+  (let ((path (mapcar 'file-truename
+                      (append exec-path
+                              (split-string (getenv "PATH") path-separator t)))))
+    (setenv "PATH" (mapconcat 'identity (delete-dups path) path-separator))))