PR merged into nvim-lspconfig; Make sure to update nvim-lspconfig and your nvim config accordingly! Directions are in the README

[Feel-ix-343]

that it.

Mason, brew, helix, zed, and VSCode extension are all on the way!

[adriangalilea]

@Feel-ix-343 where to keep track for the helix one?

[Feel-ix-343]

1. Hey so you can use all of the features through the nvim language server protocol. Most will set up their own keymappings to the nvim lsp functions. For example: to get the definition of the link under the cursor use a mapping to vim.lsp.buf.definition (I think thats the name). It seems like you are using something like Lazyvim, so check the docs for mappings it makes.

2. And for the directory problem, opening an issue would be great. My initial reaction is that the lsp is not reading your home directory as a note directory-- so it may not be a performance issue. Is your notes directory a git directory? Right now moxide only initializes on git directory

3. Make sure you have the lsp file watcher enabled. Check the readme for instructions on this.

Thanks for reporting and please open an issue. These config issues are certainly something to iron out before we get our of prerelease

[adriangalilea]

It seems like you are using something like Lazyvim

Helix, so not sure how those things apply.

Is your notes directory a git directory? Right now moxide only initializes on git directory

I see I see, my directory wasn't git, thank you for pointing that out, I think that should be very clear on the README.md :)

Thank you, yeah, was considering opening an issue but didn't.

[Feel-ix-343]

Its a bug right now; It should work for any cwd; I will update the ls soon.

[adriangalilea]

Is there an github issue to keep track of?

[Feel-ix-343]

Hey!

It is here: #44

[David-Else]

Support was merged into Helix:

helix-editor/helix#9758

https://github.com/helix-editor/helix/wiki/Language-Server-Configurations#markdown-oxide