Wrapping my head around init-org.el -- running on Linux

[ncouture]

I've been used to customize Bernt Hanson's org-mode.org also exported in HTML via archive.org configuration for years and am seeing you state that parts of your opinionated org-mode configuration is based in his, I have no doubt but find it hard to find out what's common to me in it and what's not.

I cannot claim to be familiar with GTD in other settings than by using Bernt's workflow to the best of my ability and admitedly likely using at most 50%-75% of its workflow on my best days.

That said things simple like setting deadlines, reminders, "clocking-in when work starts, on a default task" then clocking into whatever project's task I work on, then clocking out, with fallback to parent task or "default task with unique :ID: tag does not strike me as available in your configuration, is this correct or am I missing something or is this supposed to work but don't in my environment?

That's all for now, again, thanks for sharing the good stuff!

emacs.d/lisp/init-org.el

Line 55 in 66c9128

;; Lots of stuff from http://doc.norang.ca/org-mode.html

[purcell]

Hey, yeah, it's a really long time (10+ years?) since I used the GTD stuff. I think it should all still work, but the quoted behaviours are ones I don't recall using/supporting.

[ncouture]

We spoke in a different channel (chat) about your .emacs.d/ repository not becoming a type of Emacs distribution where many contributors end up adding functionality to it.

I think your implementation though init.el and lisp/ init-*.el libraries in addition to the support for init-local.el provides the perfect setup for doing this so I'm very comfortable having my own branch, and keeping you repository as upstream, only adding your upstream changes in my .emacs.d/ when I confirm nothing breaks my additions.

This is how I use init-local.el support. Since I don't want to modify your init.el at all, I leave it as-is, in site-lisp/init-local.el I add my own version of your lisp/ directory named user-lisp/ like so:

(add-to-list 'load-path (expand-file-name "user-lisp" user-emacs-directory))

Followed by the explicit import of my init-*.el libraries.

The result currently looks like this:

;;; init-local.el --- user customization over github.com/purcell/emacs.d -*- lexical-binding: t -*-
;;; Commentary:
;;; https://github.com/purcell/emacs.d/?tab=readme-ov-file#changing-themes-and-adding-your-own-customization
;;; Code:

(add-to-list 'load-path (expand-file-name "user-lisp" user-emacs-directory))
;; (require 'typo)
;; (require-package 'company)
;; (global-company-mode)
;; (typo-global-mode)
;; (require 'init-pragmatapro)
(require 'init-gptel)
(require 'init-javascript-extras)
(require 'init-org-pdf-theme)
(require 'init-pass)
;;(require 'init-github-copilot)
;;(require 'init-python-tools)
;;(require 'init-spelling-tools)
;;(require 'init-keybindings)
;;(require 'init-utilities)
;;(require 'init-navigation)

(provide 'init-local)
;;; init-local.el ends here

In the past I remember implementing code that overwrote some of your settings in sets of files lisp/init-*.el which ended up causing me issues and I ended up with a fork that was hard to maintain as I would have to debug when upstream changes would make my downstream "behavior overridings" stop functioning as expected or raise errors.

Now that I found out this is the perfect way to stay up to date with your upstream which provides great core sanityinc Emacs functions and a very sane defaults IMO, I'm wondering how I would be able to implement my favorite functionalities from Bernt Hanson's org-mode.el world-class, self-documented, configuration without overriding your org config.

Any tips?

Should I start by doing it in one of my user-lisp/ and make it work then present it to you for review?

Thanks again, keep up bringing sanity in our environments! 🌳