No description
Find a file
2023-05-29 13:57:59 -05:00
elpa@c5f94624d2 Update [2023-04-14 Fri 22:30] 2023-04-14 22:30:48 -05: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 Only do this at work 2023-05-29 12:54:03 -05:00
prompts No interactive prompts in noninteractive mode 2023-02-27 21:15:23 -06:00
res Removed old files 2023-05-29 10:56:17 -05:00
submodule Weird, mu submodule got into a weird state 2023-03-03 09:13:29 -06:00
tests Don't rely on ~/.emacs.d in the test file 2023-02-27 21:19:18 -06:00
tree-sitter@4ea65c5d11 Added tree-sitter submodule 2023-04-15 11:02:51 -05:00
.gitignore Updated gitignore 2022-12-17 16:54:41 -06:00
.gitmodules Added tree-sitter submodule 2023-04-15 11:02:51 -05:00
config-ext.org Move this to ext 2023-05-29 12:24:28 -05:00
config-exwm.org SO MUCH POWER, I can save in EXWM buffers 2023-04-29 17:02:44 -05:00
config-min.org Move this to ext 2023-05-29 12:24:28 -05:00
config-org.org Find projects 2023-05-29 13:57:59 -05:00
config-programming.org Out with company, in with corfu 2023-05-20 15:36:43 -05:00
config-submodules.org This is slowing down emacs too much 2023-03-17 16:33:04 -05:00
helpers.org Reduce dependence on ~/plaintext 2023-04-29 14:12:50 -05:00
init.el Dependencies rearrange 2023-04-18 12:49:01 -05:00
my-etzy.el Accidentally swapped these two 2020-08-01 12:34:57 -05:00
my-redefs.org Revert "Can I do this? Lisp expressions in tangle argument" 2023-03-20 05:16:46 -05:00
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 Need this, or need to re-byte compile xcb-ewmh.el 2019-06-28 11:12:36 -05:00

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.