Config not being used #127
Comments
|
Can you post the LSP's log? I suspect that parsing your config file failed, which caused the server to use a default config ( |
|
|
I installed |
|
Gotcha. I'm not able to reproduce locally, so I'm not entirely sure why but the server is failing to find the project specific config file. I've added some additional logs to the config parsing related code in #128. If you could pull down the latest copy from git once that's merged again and post the logs again, that would be incredibly helpful :). |
|
It says that it failed to detect project root, even though I have a git instance. |
|
Just to be sure, are you launching your editor from within the project's root directory? Are you using a much older/newer version of (Neo)vim? I'm not sure what could be causing this, but I'll spend some more time looking into it. Thanks so much for the quick responses! |
Here's more about my environment:
Also, just a note: |
|
Here's the lsp log when running on |
|
Reading through the initialization parameters, I found that we can also check the (deprecated) The fact that it's working with one project and not another leads me to believe that the neovim client isn't communicating the correct information to the server at start time. I found a few open issues with similar sounding problems in the nvim-lspconfig repo, so maybe this is something similar. Some suggested solutions (for example) include adding additional root markers. Maybe adding I'm really sorry this still isn't working! As a temporary workaround, you can also create a global configuration file. This won't override the configs for any projects where the local config is being detected correctly. Based off of the logs you posted earlier, I believe the correct place for this is |
This comment was marked as spam.
This comment was marked as spam.
|
It works now!! Thanks~ It seems weird to me that root_path is the solution as I don't have it configured for I appreciate your effort, thanks again. 
|
|
Glad to hear it! Thanks for working through it with me!
That is pretty odd. The global config directory is chosen based off of the |
Maybe, I don't know about that create. But, for future revisions, my opinion is that a global config must be placed at |
That seems reasonable. I think it makes sense to still search in that directory (I'm sure it's set up that way for a reason), but I can add a secondary check for the more intuitive path. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
I disabled
x86_64instruction set and enabledarm, however I still see information aboutx86_64but notarm. I'm not sure if I have something wrong in my setup.Here's an screenshot of my setup (git was initialized):
Also,
asm-lspwas installed with cargo from git.The text was updated successfully, but these errors were encountered: