doct VS dot-doom

Doct! Writing org capture templates is a PITA.

For such a compelx logic in templates, I recommend (function function-returning-the-template) templates. Or you can explore https://github.com/progfolio/doct

https://github.com/progfolio/doct implements a way for templates to inherit from a parent group or template. There were plans to use doct in org-roam early on, but I no longer contribute to the project and I think it has continued down the path of using its own extensions to capture templates.

I use doct which I would advise to use as well if you want to write your templates more clean

also see: https://github.com/progfolio/doct for org-capture definition sugar

I have a capture template for Waiting For items, examples: * Waiting For ** WAITING Dan the Book man send me an invoice [[mu4e:msgid:[email protected]][Re: Looking for great books of the western world]] [2022-02-25 Fri] ** RECEIVED Doct maintainer respond to my [[https://github.com/progfolio/doct/issues/33][support query]] [2022-02-27 Sun] ** RECEIVED Dok van Putten respond to my [[mu4e:msgid:[email protected]][request RE Covid booster shot]] [2022-02-25 Fri]

https://github.com/progfolio/doct#hooks

I switched from a hand-maintained config to Doom last year, and I can highly recommend it. It's very well organized, the community is very friendly and it works great. If you are interested, my config is at https://github.com/zzamboni/dot-doom/blob/master/doom.org.

This sets the default for all the emacs-lisp blocks in the file, but you can still selectively write other blocks to different files, or not at all by specifying :tangle no. This way you can easily tangle multiple destination files from a single Org file. For an example, you can see my doom.org file, from which Doom's init.el, config.el and packages.el are all tangled.

In my config I have a hook I can call after saving the .org file to automatically export it and update the open browser to the current slide. This makes the process of updating/viewing the presentation a lot smoother. You can find my config here: https://github.com/zzamboni/dot-doom/blob/master/doom.org#revealjs-presentations

Note that I said my "old config". A few months ago. I decided to try Doom Emacs. Over a couple of days, I ported most of the important bits of my decades-old, hand-maintained config, and in the process realized I could get rid of a lot of scaffolding (like the whole package-management bits in your config) by virtue of Doom's existing mechanisms, and also I could omit a lot of the configuration because Doom includes decent defaults for many things. I have not regretted moving to Doom. You can find my new config at https://github.com/zzamboni/dot-doom/blob/master/doom.org.

If you use use-package, it works well to define the package to be loaded :after org. I have lots of examples in my old emacs config, for example: (use-package ox-hugo :defer 3 :after org :custom (org-hugo-use-code-for-kbd t)) I now use Doom Emacs, but the same technique can be used with use-package!. For example, from my Doom Config: (use-package! ox-leanpub :after org :config (require 'ox-leanpub-markdown) (org-leanpub-book-setup-menu-markdown)) HTH