colonelpanic8
confused : project vs projectile
Shouldnt using the package org-projectile automatically set the projectile backend?
It would be nice to see a sample projectile use-package sample config.
Originally I just had a "usepackage org-projectile" form, but the docs say I need org-project capture and then to also include org-projectile. I'm pretty confused between project and projectile at the moment as the word "project" seems to have multiple meanings : generic "project" and also emacs "project.el" handling ;)
org-projectile functions are a backwards compatibility layer.
The new way to to do things is just to use org-project-capture with the org-projectile backend.
IMHO the whole concept of make-instance to set the backend in the users configuration while an instance is already created in the default config isn't sound.
It also doesn't really work with defcustom.
@Thaodan You can arbitrarily customize the behavior by composing/making instances. I'm not sure why an instance being created as the default matters at all, it wont get used unless its set to the value.
It also doesn't really work with defcustom.
I would argue that defcustom isn't really sound and it's a feature mostly for noobs and people that probably shouldn't be using emacs anyway.