Provide option for easier module loading.

[UristMcLisper]

Provide option for easier module loading.

[jeffbowman]

Closing this as there is no further discussion, and v2 has been released

[jvdydev]

Interesting thought, I wonder if such a function would be more likely to end up in a documentation snippet instead (something like "I want everything, is there a faster way?").

I think the code you provided as a "quick fix" would need a bit of transformation.

On a principles level, I'm not sure if this would abstract too much away (hence I'd rather put it in documentation so people can understand what they are using), hope that makes sense.

[UristMcLisper]

I'll clarify. I'm proposing this snippet to be mentioned in Getting Started README and 4.2.2 Emacs Initialization:

(crafted-emacs-load-modules
 '(completion
   defaults
   ide
   lisp
   org
   package
   speedbar
   ui
   updates
   workspaces
   writting
   ;; home
   ;; evil
   ;; osx
   ;; screencast
   ))

Append "-packages" or "-config" to any of symbols to choose it only.

[jvdydev]

Sorry, I was/am rather tired reading this, however I think I understand.

I don't think putting a crafted-emacs-load-modules function into the project would make a ton of sense (ignore this section if this was not the intention).
It's not much different from a package installation macro (except it being a function).
I think this would fit more into an example documentation to be pasted into a users init.el file (both the function and the function call).

Maybe @jeffbowman has some thoughts as well.

[jvdydev]

I'm also a little confused as your initial issue provided a way to exclude packages while the second example seems to be more focused on including packages (and that's how I remember it working in Doom Emacs as well back when I used it).

[UristMcLisper]

Yes, my bad. Removed it

[jeffbowman]

I don't think putting a crafted-emacs-load-modules function into the project would make a ton of sense.
It's not much different from a package installation macro.
I think this would fit more into an example documentation to be pasted into a users init.el

I agree.

This probably belongs more in a "Tips and Tricks" section in the documentation.