-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support relative paths in the command and generate a config file in .idea
that can be committed
#336
Comments
I wonder if we fill the workspace directory with project root path, it will fix your issue. Ifbit is working we should perhaps provide a New field working directory filled by défaut with the project root path. @fbricon what do you think about that? |
Inteliij has macro fields so this complexity is abstracted away |
Could you explain more your suggestion please. |
So macro fields can contain pre-defined values that expand, this is great for shared config. |
Thanks so much @KotlinIsland for your great idea. I didn't know this macro syntax and it is indeed a great idea. I have created a PR for that at https://github.com/redhat-developer/lsp4ij/pull/340/files (with some documentation), hope you (and @DetachHead ) will like it |
You can now uses macro, see doc at at https://github.com/redhat-developer/lsp4ij/blob/main/docs/UserDefinedLanguageServer.md#macro-syntax |
awesome that works, thanks! only other thing is being able to commit the language server config. i will raise a separate issue for that |
for my use case, the language server will always be located at
.venv/scripts/basedpyright-langserver.exe
(on windows at least). ideally i would be able to just enterbasedpyright-langserver
as the command and it would pick it up from the current sdk:specifying the full path works, but that's not ideal because i would like the language server to be saved in a config file that i can commit, so that others in my team can have the LSP configured automatically without them having to set it up themselves
The text was updated successfully, but these errors were encountered: