Unable to initialise Ruby LSP vscode plugin on Windows/Powershell due to changes in #2552

[mattys101]

Description

There appears to be a regression introduced by fixes from pull request #2552 on Windows with Powershell command execution.
The newly modified command with the "separator" text:

ruby -W0 -rjson -e 'STDERR.print("RUBY_LSP_ACTIVATION_SEPARATOR" + { env: ENV.to_h, yjit: !!defined?(RubyVM:: YJIT), version: RUBY_VERSION }.to_json + "RUBY_LSP_ACTIVATION_SEPARATOR")'

appears to be having the double quotes stripped out at some point resulting in a 'constant RUBY_LSP_ACTIVATION_SEPARATOR not initialized' error.

Alternative quotings such as:

ruby -W0 -rjson -e 'STDERR.print(''RUBY_LSP_ACTIVATION_SEPARATOR'' + { env: ENV.to_h, yjit: !!defined?(RubyVM:: YJIT), version: RUBY_VERSION }.to_json + ''RUBY_LSP_ACTIVATION_SEPARATOR'')'

and:

ruby -W0 -rjson -e "STDERR.print('RUBY_LSP_ACTIVATION_SEPARATOR' + { env: ENV.to_h, yjit: !!defined?(RubyVM:: YJIT), version: RUBY_VERSION }.to_json + 'RUBY_LSP_ACTIVATION_SEPARATOR')"

Appear to work correctly in manual testing.

Ruby LSP Information

Version 0.8.0

Version Manager: none

Reproduction steps

1. Start the Ruby LSP using VSCode
2. Open a Ruby file
3. Error notification that Ruby LSP activation failed

Code snippet or error message

Automatic Ruby environment activation with none failed: Command failed: ruby -W0 -rjson -e 'STDERR.print("RUBY_LSP_ACTIVATION_SEPARATOR" + { env: ENV.to_h, yjit: !!defined?(RubyVM:: YJIT), version: RUBY_VERSION }.to_json + "RUBY_LSP_ACTIVATION_SEPARATOR")' -e:1:in `<main>': uninitialized constant RUBY_LSP_ACTIVATION_SEPARATOR (NameError)

[vinistock]

Thank you for the bug report! This broke due to that PR indeed. The attached PR should fix it.

[vinistock]

We just released v0.8.1. Please report back if you find any issues!

[mattys101]

Fantastic. Thanks. Running into #2604 now, but otherwise all good.