Creating an org-capture template items (i.e. tasks) in my denote inbox-file #431
Replies: 2 comments
-
From: "Lukas C. Bossert" ***@***.***>
Date: Wed, 11 Sep 2024 14:32:16 -0700
In my workflow I write down tasks and have them stored as TODO items in an inbox-file.
I used to do it with an org-roam-capture template:
```
("i" "inbox" plain
"* TODO %^{Title|${title}} %^G\n%^{time|SCHEDULED:|DEADLINE:} %^t\n:PROPERTIES:\n:CAPTURED: %U\n:END:\n%?"
:target (file+head "Inbox.org"
"#+TITLE: Inbox\n")
:empty-lines 1
)
```
[... 32 lines elided]
If I understand this correctly, you are creating a new entry inside of
the same file, not a new file each time, right? If so, why not do this
with the regular org-capture-templates?
Denote does not need to be involved in this step. Then, if you need to
split out the heading into its own standalone file, you can use the
command 'denote-org-extras-extract-org-subtree'.
…--
Protesilaos Stavrou
https://protesilaos.com
|
Beta Was this translation helpful? Give feedback.
0 replies
-
You are quite right - it doesnt make a lot of sense to write a function and make things more complicated. I set the new file as destination which has the denote naming-scheme. Everything is fine now. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In my workflow I write down tasks and have them stored as TODO items in an inbox-file.
I used to do it with an org-roam-capture template:
I was able to re-create the template using a function which is now storing the TODO items a denote file:
But since I don’t like custom functions like this and would favor org-capture template for it,
I was wondering how I would write a proper denote-org-capture template for this.
------ EDIT
I was giving it a try with
denote-templates
:but it creates first a file and prompting for a title etc and then it calls the function.
Beta Was this translation helpful? Give feedback.
All reactions