Open krisbalintona opened 1 week ago
Thank you for your interest and for finding time for feedback!
You are right, there is no recommended way for integrating with org-capture-templates
yet. Indeed, the transient menu could be a way to organize org-catch commands. Good suggestion! I did not think of it because i either bind-key
my org-catch
commands and rely on muscle memory or just M-x
it by name.
Adding to your suggestion i thought of the following org-capture
friendly features:
org-catch
command that somehow injects it into org-capture
dispatcher.org-catch
commands (e.g., list commands with org-catch-*
prefix).org-capture-templates
to org-catch
templates/commands. (The user will need to come up with proper command names because org-capture only has description and key binding.)Please, let me know what you think. What feature is the most missing? Maybe some more ideas?
@ergopractice Thanks for giving a few of your thoughts.
Personally, I'm most preferential to the first option (integration with the existing functionality of org-capture
). This makes using the built-in functionality to using org-catch seamless. However, I haven't looked at the org-capture
internals, so I don't know how feasible this is.
Perhaps the second most convenient alternative would then be the third option: porting the user's built-in org-capture-templates
to an org-catch variant that also shows the org-catch-specific templates a user defines.
Awesome package!
I did have a question though: what is the recommended way to integrate with the existing
org-capture-templates
? As far as I can tell from the README, users would have to, say, create a transient menu of their own that is separate fromorg-capture-templates
.