Just now getting started w/ org-roam – I have to say, it’s been pretty smooth so far, have been using it fr just a couple of hours and it’s felt incredibly rewarding.
Sitll, I’m notiicng a friciton point that I bet other people have solved. Right now I’m taking notes on a large-ish collection of web pages. My workflow involves going to firefox, clicking the org-roam bookmarklet, and then taking notes on the page. I often feel like I want to create a tag of some kind to a concept, and since my repo is brand-new, those links/tags are almost always non-existent. org-roam chokes on the recursive capture process, and so I have to stop editing my main note, complete the capture with C-c C-c, and then find the file again before I can start editing again . So what I’m wondering is if there’s a way to keep the cpatured note in focus in the current window after I complete the capture? If that were the case I could go straight back to editing the note, and there’d be little mental overhead/interruption of thought.
In the meantime, what you can do is add :immediate-finish t to the relevant template in org-roam-capture-templates or org-roam-capture-ref-templates (for the ones created via Org-protocol). This will directly create the file for you, thereby circumventing the need for nested processes. However, bear in mind that if you want to cancel that capture, since it has immediately finished, you’ll need to remove the file yourself.
ah, thanks @zaeph. I used that trick, though I found I also needed to customize org-capture-after-finalize-hook by adding org-capture-goto-last-stored. I tried just customizing org-roam-capture-after-find-file to restrict this behaviour to org-roam capture templates, but that didn’t seem to do what I expected (open the new file immediately after capture).
