Replies: 6 comments
-
I have a feeling that it's related to #375. At least, that's not the first time I see nvim with mason behaving weirdly. @bytebeast could you show the part of the logs that corresponds to the LSP initialization request? The relevant entry has
Let me give a bit more color on this. Marksman will try to do a recursive scan only within a workspace folder that is communicated by the LSP client (an editor). More specifically, when neovim start marksman, it sends it an initialization request. As part of this request's payload it sends rootUri or rootPath. Then:
To experience the behavior as you described, nvim would need to send your home dir as More on this in: https://github.com/artempyanykh/marksman/blob/main/docs/features.md#workspace-folders-project-roots-and-single-file-mode |
Beta Was this translation helpful? Give feedback.
-
@bytebeast perhaps easier, the output of |
Beta Was this translation helpful? Give feedback.
-
I just noticed that this is LazyVim. And I seem to be able to reproduce the problem with stock LazyVim on my end. |
Beta Was this translation helpful? Give feedback.
-
Ok, I found that "home folder as a root" comes from the nvim sending the following notification:
I don't have this with my own config. Unclear, where does this come from. |
Beta Was this translation helpful? Give feedback.
-
its just the current working directory where the foo.md file is opened.
guessing it gets passed in via lazyvim(mason) ? ( /shrug )
errors only seen when opening md files in my home directory. i have a
vanilla lazyvim config with markdown "extra" plugin provided by lazyvim.
…On Fri, Dec 13, 2024 at 1:16 PM Artem Pianykh ***@***.***> wrote:
Ok, I found that "home folder as a root" comes from the nvim sending the
following notification:
[DEBUG][2024-12-13 21:13:56] .../vim/lsp/rpc.lua:286 "rpc.send" { jsonrpc = "2.0", method = "workspace/didChangeWorkspaceFolders", params = { event = { added = { { name = "/Users/<USERNAME>", uri = "file:///Users/<USERNAME>" } }, removed = {} } }}
I don't have this with my own config. Unclear, where does this come from.
—
Reply to this email directly, view it on GitHub
<#377 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AET32OQBYYSJJAKZ5IDLFBL2FNFB5AVCNFSM6AAAAABTQEENUGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNJWGIYDGNA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
I think #380 should address it. Also LazyVim/LazyVim#5074 |
Beta Was this translation helpful? Give feedback.
-
these errors seem to only occur when i open a *.md file in my parent home directory. unclear why its trying to read all the sub-directories.
sample entries from lsp.log:
I don't have marksman manually configured in
~/.config/nvim/lua/plugins
. As far as I can tell it gets loaded from~/.local/share/nvim/lazy/LazyVim/lua/lazyvim/plugins/extras/lang/markdown.lua
Not sure if this a bug, or if its something i unknowingly broke on my setup.
I don't have any lsp configs in plugins. Im currently only using whats loaded through extras.
These errors only appear when editing a markdown file in my home directory which leads me to believe it recursively scans all subdirectories of the file your editing. Guessing this is becasue you can link to other markdown files from a single markdown file?
Is there a way to disable the recursive scans from specific directories OR only enable recursive scans of specific directories OR maybe just the ability to disable recursive scans all together?
Beta Was this translation helpful? Give feedback.
All reactions