Useage Patterns Current and Anticipated

My emacs revisions are in testing. I want to anticipate what I will need when I place these changes in production.

Main focus of Emacs.org -> init.el

• Emacs itself
• Coding - Computer Languages
• Common Lisp, Slime and various implementations
• Org Mode
  • General use in Coding
  • General use in personal projects
  • org-agenda - gtd - personal time/organization
  • org-capture - this works with gtd and medical things.
  • org-publish - a collection of various technical writings

emacs.d porting cases

• for Coding - the last two weeks demonstrate how this works
• Org for Coding - this also works
• gtd is an there can only be one type of thing.
  • very good for long term project like bureaucratic applications, taxes and such
• org-capture
  • gtd entry stuff
  • medical and appointment collection stuff

on new config forks

• gtd is likely not going to be used largely bound to DESKER-zzzap
• custom agenda items are bound to gtd largely bound to DESKER-zzzap
• custom medical stuff is largely bound to DESKER-zzzap
• org-publish will need to be explored and refactored
• Coding and general org editing could be anywhere.

new fork focus

• gtd agenda - a per-user feature agenda - how to structure this?
• gtd agenda - a basic per-user or per-project frame work to start with.
• org-publish

Quick conclusion

• gtd and agenda items in DESKER-zzzap are the most configured
  • move that stuff into scripts
• make Emacs.org less gtd specific but agenda aware.