No description
Find a file
2022-12-05 17:50:57 -06:00
elpa@e7d39f67c0 No rustic on puppet's computer 2022-12-04 12:25:31 -06:00
exwm-x More exwm configs 2021-04-07 20:02:17 -05:00
legacy Archive old programming configuration 2022-06-12 05:28:11 -05:00
lisp Move mail configuration back to emacs 2022-12-05 17:50:57 -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 Cleaned up tests, added new macro 2022-09-30 07:54:27 -05:00
.gitignore Added elpa as submodule 2022-10-28 15:04:21 -05:00
.gitmodules Use submodule instead for code-compass 2022-11-25 08:25:52 -06:00
agenda-files.el New org mode setup 2019-05-10 12:43:48 -05:00
config-ext.org Oops, indentation 2022-12-05 14:44:54 -06:00
config-exwm.org Same for exwm 2022-10-16 06:06:07 -05:00
config-min.org Move buffer-window management to ext 2022-12-04 11:44:54 -06:00
config-org.org Promote this keybinding to use-package 2022-11-07 16:27:25 -08:00
config-programming.org No rustic on puppet's computer 2022-12-04 12:25:31 -06:00
config-submodules.org Move some configuration to config-submodule.org 2022-11-25 08:25:55 -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 Moved workspace-counsel to file, disable cause of workgroups 2019-12-26 11:01:48 -06:00
init.el Move mail configuration back to emacs 2022-12-05 17:50:57 -06:00
my-bookmarks Change org agenda root folder 2020-08-23 11:51:11 -05:00
my-etzy.el Accidentally swapped these two 2020-08-01 12:34:57 -05:00
my-redefs.org Advice this 2022-09-12 13:45:12 -05:00
neo.ahk Create neo.ahk 2020-08-07 21:36:05 -05:00
README.org i GUESS i gotta have one of these :/ 2021-04-07 21:00:20 -05: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.