Open bbigras opened 4 years ago
I don't think this is feasible without #5.
Can you give me an idea what the file/directory layout looks like when using org-roam? Are all the files stored in the same directory? Are the links relative links like [[./other-file.org][other file]]
?
It seems some people are using subdirectories (see https://github.com/org-roam/org-roam/issues/218) and the "daily" notes are inside a subdir.
link example
[[file:../20210405235900-materialize.org][materialize]]
layout example
├── 20210331165046-note1.org
├── 20210405235900-note2.org
├── daily
│ ├── 2020-11-13.org
│ ├── 2020-11-14.org
There's also an sqlite database (org-roam.db). I'm sure all the links are indexed in there.
Btw, org-roam is going thru a major redesign, see https://github.com/org-roam/org-roam/pull/1401
Org-roam V2 does not recognize file links.
https://github.com/org-roam/org-roam/wiki/Hitchhiker's-Rough-Guide-to-Org-roam-V2#node-id-and-links
Thanks.
I am working on implementing relative links.
I am definitely not planning on supporting any sort of DB.
Relative file links to Org Mode files are now supported in v1.18.1.
However references to sections (by title or by ID) are not resolved yet. It seems like that is quite important for Org Roam support, right? Or will such links no longer be used in v2? What is the timeline for v2?
Afaiu, v2 is based solely on ID links. No idea about the timeline, but there is a first alpha available and @jethrokuan is plowing ahead at full speed 😄
However references to sections (by title or by ID) are not resolved yet. It seems like that is quite important for Org Roam support, right? Or will such links no longer be used in v2? What is the timeline for v2?
v2 is centered around ID links.
No idea what the timeline is for v2 either, just continually fixing bugs and bringing improvements until it feels ready for public release.
v2 is centered around ID links.
No idea what the timeline is for v2 either, just continually fixing bugs and bringing improvements until it feels ready for public release.
Thanks for the information, @jethrokuan.
Is that id:
links or #custom-id
links?
Is that id: links or #custom-id links?
id: links.
Thanks.
I plan to support local id:
links and #custom-id
links (linking to sections in the same file) in the next release.
I will also support file:
links with #custom-id
fragments pointing to other files.
However I don't see a lightweight way to support id:
links that point at other files. I'm not really keen on implementing indexing machinery or trying to read prebaked index DBs (if such a thing exists).
v1.19.0 is out for all platforms.
v1.40.4 is now available on all platforms.
I guess then the remaining thing that needs to be done to better support Org-roam is searching for titles?
It's kinda hard to navigate org-roam files without org-roam.
it lets you search for titles:
#+title: note title
and show backlinks.