Posts

This had to happen eventually.

I modified a Perl lbdb backend by ‪@[email protected] ‬to use my org-contacts with mutt

I don’t like the looks of any of the personal CRM software out there, so I’m making a plaintext one.

More ChatGPT and org, using the org agenda, Yellowjackets again, Doom keybindings

I went in unsure how it could work, came out pretty sure it did work, and I think I understand why.

I finally took the time to play with ChatGPT to configure Emacs and write some Ruby.

Some ruby wired up to mutt macros allows for on-the-fly sender scoring and a color-coded message index.

As always, a plaintext revival means a mutt revival.

Cross-posting is failing and I’m not sure why I am keeping a Twitter account.

My historic pattern for descending into Emacs hell has always started with the kitchen-sink init, and the path to recovery has always involved a patient refactoring into multiple files: Some kind of “the basics,” something just for org, something for odd little quality of life things, and a quarantine file where new stuff can enjoy a probation period where I can bisect it first when something goes wrong. If I add a big chunk of functionality from a new mode, that might get its own file, too. ...