mjlbach
Modularity suggestion
I know this is WIP, and that you want to keep this super focused and minimal, but I wonder if you might consider adding some way for users to add their own modules to a subdirectory, without them having to figure out how to do this themselves, and modify the main init.el file?
Say adding something like:
(add-to-list 'load-path (expand-file-name "lisp" user-emacs-directory))
... and then, I dunno, some standard feature init.el will load, which can in turn load other user features, like:
;;; init-user.el --- user init -*- lexical-binding: t; -*-
;;;
;;; Code:
(require 'init-bd) ; my stuff
(provide 'init-user)
;;; init-user.el ends here
Could have the benefit that one can still easily update the main init.el file as it evolves, and also demonstrate how to modularize functionality into separate files/features.
Maybe as a commented block with an example init-user.el? I imagine if people are going to download/use this they are likely to want to change all of the use-package blocks in the main init.el.
