Closed skjbulcher closed 3 months ago
Can you open Sublime Text in safe mode and then open the console and run
import os; print(os.environ["PATH"])
And could you just run LSP: Troubleshoot Server
for LSP-copilot and paste the result here?
I have found the culprit is in lsp_utils
. I will file a PR there soon.
Note that I keep a lot of windows
This triggers the bug.
Can you open Sublime Text in safe mode and then open the console and run
import os; print(os.environ["PATH"])
>>> import os; print(os.environ["PATH"])
/home/[USERNAME]/google-cloud-sdk/bin:/home/[USERNAME]/.nvm/versions/node/v21.6.2/bin:/home/[USERNAME]/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/home/[USERNAME]/.local/bin
And could you just run
LSP: Troubleshoot Server
for LSP-copilot and paste the result here?
## Server Configuration
- command
```json
[
"${node_bin}",
"${server_path}",
"--stdio"
]
"/home/[USERNAME]/.cache/sublime-text/Package Storage/lsp_utils/node-runtime/18.18.1/node/bin/node" "/home/[USERNAME]/.cache/sublime-text/Package Storage/LSP-copilot/18.18.1/language-server/node_modules/copilot-node-server/copilot/dist/language-server.js" --stdio
source | text | embedding
source | text | embedding
{}
{
"auto_ask_completions": true,
"commit_completion_on_tab": true,
"completion_style": "popup",
"debug": false,
"hook_to_auto_complete_command": false,
"local_checks": false,
"proxy": "",
"telemetry": false
}
{
"PATH": "/home/[USERNAME]/.cache/sublime-text/Package Storage/lsp_utils/node-runtime/18.18.1/node/bin:/home/[USERNAME]/.cache/sublime-text/Package Storage/lsp_utils/node-runtime/18.18.1/node/bin:/home/[USERNAME]/.cache/sublime-text/Package Storage/lsp_utils/node-runtime/18.18.1/node/bin:/home/[USERNAME]/.cache/sublime-text/Package Storage/lsp_utils/node-runtime/18.18.1/node/bin:/home/[USERNAME]/.cache/sublime-text/Package Storage/lsp_utils/node-runtime/18.18.1/node/bin:/home/[USERNAME]/.cache/sublime-text/Package Storage/lsp_utils/node-runtime/18.18.1/node/bin:/home/[USERNAME]/.cache/sublime-text/Package Storage/lsp_utils/node-runtime/18.18.1/node/bin:/home/[USERNAME]/.cache/sublime-text/Package Storage/lsp_utils/node-runtime/18.18.1/node/bin:/home/[USERNAME]/.cache/sublime-text/Package Storage/lsp_utils/node-runtime/18.18.1/node/bin:/home/[USERNAME]/.cache/sublime-text/Package Storage/lsp_utils/node-runtime/18.18.1/node/bin:/home/[USERNAME]/.cache/sublime-text/Package Storage/lsp_utils/node-runtime/18.18.1/node/bin:/home/[USERNAME]/.cache/sublime-text/Package Storage/lsp_utils/node-runtime/18.18.1/node/bin:/home/[USERNAME]/.cache/sublime-text/Package Storage/lsp_utils/node-runtime/18.18.1/node/bin:/home/[USERNAME]/.cache/sublime-text/Package Storage/lsp_utils/node-runtime/18.18.1/node/bin:/home/[USERNAME]/.cache/sublime-text/Package Storage/lsp_utils/node-runtime/18.18.1/node/bin:/home/[USERNAME]/.cache/sublime-text/Package Storage/lsp_utils/node-runtime/18.18.1/node/bin:"
}
None
{
"auto_complete_selector": null,
"lsp_active": null,
"syntax": null
}
[]
{}
The upstream has merged the fix so we just have to wait for its new release.
I have an issue that I am trying to troubleshoot:
This issue most frequently occurs when I open a Sublime Text new window. However, it does occasionally occur in code windows as well. Today I had to find and click on the error quite a few times in order to access Sublime Text, which is a problem.
While I was searching around for ways to troubleshoot the issue, I discovered this when running LSP: Troubleshoot Server:
Note that I keep a lot of windows and tabs open in Sublime Text from time to time.
Running "LSP: Dump Window Configs" yielded this result for env:
Depending on the window, the env is repeated more or less. I suspect that each window appends to the env, without any duplication.
I don't know if the "argument list too long" issue has anything to do with the environment, but even if it isn't the env could be handled better.