No description
Find a file
2023-03-01 10:58:45 -06:00
elpa@08be23f8d3 Bump elpa revision 2023-01-03 08:38:24 -06:00
exwm-x More exwm configs 2021-04-07 20:02:17 -05:00
legacy Stop relying on "~/.emacs.d" 2023-03-01 10:58:45 -06:00
lisp Stop relying on "~/.emacs.d" 2023-03-01 10:58:45 -06:00
prompts No interactive prompts in noninteractive mode 2023-02-27 21:15:23 -06:00
res Updated width of emacs logo 2022-06-14 12:34:15 -05:00
submodule Mail is now being configured elsewhere 2022-12-04 12:41:06 -06:00
tests Don't rely on ~/.emacs.d in the test file 2023-02-27 21:19:18 -06:00
.gitignore Updated gitignore 2022-12-17 16:54:41 -06:00
.gitmodules Use submodule instead for code-compass 2022-11-25 08:25:52 -06:00
agenda-files.el
config-ext.org Stop relying on "~/.emacs.d" 2023-03-01 10:58:45 -06:00
config-exwm.org Stop relying on "~/.emacs.d" 2023-03-01 10:58:45 -06:00
config-min.org Stop relying on "~/.emacs.d" 2023-03-01 10:58:45 -06:00
config-org.org Stop relying on "~/.emacs.d" 2023-03-01 10:58:45 -06:00
config-programming.org Don't use github-ssh in noninteractive mode 2023-02-27 21:15:38 -06:00
config-submodules.org Stop relying on "~/.emacs.d" 2023-03-01 10:58:45 -06:00
de_match_keyboard This doesn't exactly belong here. I'll figure it out later 2021-04-09 13:45:46 -05:00
elfeed.org
helpers.org For sending rent 2023-02-18 11:10:36 -06:00
init.el Almost there, but need to get rid of interactive prompts 2023-02-27 20:55:16 -06:00
my-bookmarks Change org agenda root folder 2020-08-23 11:51:11 -05:00
my-etzy.el
my-redefs.org Advice this 2022-09-12 13:45:12 -05:00
neo.ahk
README.org i GUESS i gotta have one of these :/ 2021-04-07 21:00:20 -05:00
run-tests.el Almost there, but need to get rid of interactive prompts 2023-02-27 20:55:16 -06:00
test.org

My Emacs Config

If you're new here, start in init.el.

Modules will be progressively loaded from there. There's two kinds of ways I load things.

  • From a top level *.org file
  • From a tiny lisp module in the lisp/* subfolder.

Why do I do it two ways? Because in the past, I only used to do the first way. However, it became confusing to manage dependencies, and my org config blocks had to be in a certain order in order for my config to work. That was stupid, so I pulled out all of the heavy dependency related stuff into lisp modules. This made things easier, so when I #'require a top level module, it will #'require everything else that it needs. Goodbye dependency nightmares!

Loading an org file

Loading an org file will look something like this:

  (org-babel-load-file
   (expand-file-name "config-org.org"
                     user-emacs-directory))

If you want to know what this loads, then dive in to config.org! (Hint, it probably loads stuff related to org)

Loading a module from lisp folder

If you see something along the lines of:

(require 'emacs-custom-load-or-ask)

This could just be just a 3rd party emacs-lisp package. However, I've tried to stick with use-package for things I have to download from melpa/elpa/etc., so most of the requires will be for stuff locally on my system that I wrote. Look for something in the lisp/ subfolder that matches the name of the module, and you'll find what's being loaded. Most likely.

Questions?

Feel free to shoot me an email. Maybe include in the subject line something about emacs config blah blah blah.