nobiot

I don't think Org-roam has this function. I'd do either of the following: 1. Link two files (probably both ways) 2. Manually copy one to the other, but keep both...

This is the latest I find from the Discourse Forum by @wuqui https://org-roam.discourse.group/t/logseq-floss-web-outliner-compatible-with-org-roam-now/980/10?u=nobiot

@bdarcus You might have already enabled multiple nodes per ref for `org-roam-ref-find` and not sure if this is helpful. This small change below allows me to have a same single...

For `org-roam-node-from-ref`, we may need to consider returning a list of all the nodes, rather than a single one -- `org-roam-node-nodes-from-ref` perhaps. Not sure if there is any other functions...

Just to return multiple nodes, the following works on my end; `org-roam-node-from-ref` now returns a list of nodes for one ref: ``` diff @@ -280,16 +280,17 @@ (setq type "cite"...

We may need to look at graph -- ref might be used there via the protocol in addition to the website capturing.

> You mean use org-roam-node-from-ref in org-roam-ref-read--completions? No I meant the original `org-roam-node-from-ref` to stay. This does not influence `org-roam-ref-find`. > The immediate bug is caused by the fact that...

> what are you referring to here? `org-roam-protocol-open-ref`? Yes.

@bdarcus just to be sure. I re-wrote my earlier comment -- it was confusing to say the least. Really sorry if an email arrives from GitHub with my reply before...

> All that seems to do is remove the constraints from the db query there, and moves it to the `car`. Presumably (I'm missing how ATM) it also ensures that...