You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
set this environment variable (for example inside .bashrc): export RIPGREP_CONFIG_PATH=~/.config/ripgreprc
inside ~/.config/ripgreprc put "--color=always" (without quotes)
create a new test project: $ dotnet new console
launch vscode: $ code .
install the omnisharp c# extension and witness how it doesn't start the omnisharp server.
it can't launch the server, because it calls "vscode.workspace.findFiles(...)" (it's in omnisharp v.1.14.0 on src/omnisharp/launcher.ts line 48), which doesn't return any results due to the ripgrep configuration from the environment variable. findFiles will simply return an empty array without any results, but it should return one result.
workaround: i put "unset RIPGREP_CONFIG_PATH" inside the launcher of /usr/bin/code
Does this issue occur when all extensions are disabled?: Yes. on the master branch, launch the debug task called "VS Code API Tests (single folder)". the test calling findFiles will fail:
2) workspace-namespace findFiles: AssertionError: 0 == 1
The text was updated successfully, but these errors were encountered:
VS Code probably wants to use ripgrep with the --no-config option, which will prevent ripgrep from reading its configuration from the environment (forever and always).
Steps to Reproduce:
it can't launch the server, because it calls "vscode.workspace.findFiles(...)" (it's in omnisharp v.1.14.0 on src/omnisharp/launcher.ts line 48), which doesn't return any results due to the ripgrep configuration from the environment variable. findFiles will simply return an empty array without any results, but it should return one result.
workaround: i put "unset RIPGREP_CONFIG_PATH" inside the launcher of /usr/bin/code
Does this issue occur when all extensions are disabled?: Yes. on the master branch, launch the debug task called "VS Code API Tests (single folder)". the test calling findFiles will fail:
2) workspace-namespace findFiles: AssertionError: 0 == 1
The text was updated successfully, but these errors were encountered: