-
Notifications
You must be signed in to change notification settings - Fork 171
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
Ruby LSP always attempts to index the current working directory #2382
Comments
Thank you for the bug report! Let me double-check if I understand the issue correctly. We do want to index all of the files in the workspace you are working on (otherwise your project declarations would not be available for go to definition, hover, etc). What you're noticing is that BBEdit spawns the language server process using a cwd that isn't the same as the path to your workspace. Is that correct? If my understanding is right, then we need to pass down the workspace URI used to activate the server during the initialization request to the indexer so that we rely on that instead of |
I think so. This is what BBEdit sends on startup.
|
Okay, so the workspace URI is To confirm our understanding, can you please edit the Ruby LSP's code in place and print the
$stderr.puts("PWD: #{Dir.pwd}")
|
Probably worth noting this is not in VSCode |
Sorry, yeah, I said VS Code, but I just cared about the output. Indeed, our understanding was confirmed an BBEdit launches the language server process in a directory that isn't the workspace you are working on. #2424 will improve the situation, but there is a caveat explanation in the PR. |
Description
Reproduction steps
tail -f $HOME/Library/Containers/com.barebones.bbedit/Data/Library/Logs/BBEdit/LanguageServerProtocol-Ruby.txt
Code snippet or error message
The text was updated successfully, but these errors were encountered: