memory:/// locations links do not open editors

[jurgenvinju]

Describe the bug

If you have a link like so in the terminals and exists returns true: |memory:///test-modules/StartNotSuperType.rsc|(12,17,\<2,11\>,\<2,28\>), stlll clicking on the hyperlink will not open the editor.

[DavyLandman]

I think the problem is that memory:/// lives in your REPL, but not in the rascal-lsp server instance. The VS Code URI resolver talks to rascal-lsp and there it will respond: does not exist (since their own version of the memory resolver is not linked to the memory of the running REPL).

[jurgenvinju]

Yes that is it. Hard problem... The repl has a different idea of the URI registry model than the rascal LSP connector that has the VFS bridge. Different JVMs = different registry.

[DavyLandman]

I propose we close this, since what if a user has 2 REPLs open, which state of the memory resolver is the right one?

[urbanfly]

Maybe use the "authority" to disambiguate?

memory://repl-1/test-modules/file.rsc
memory://repl-2/something/else.rsc
memory://lsp-1/another/file.rsc

[DavyLandman]

Right now a user is free to use any field of the memory how they see fit. so we cannot use the authority. I think for memory file system the authority was meant as a namespace. so if you're a compiler, you would say memory://intermediate-files/ as root for your own file that you don't want to store on disk but do want to access as if they're files.