Environment extension shows wrong setting value for activation in wsl

[anthonykim1]

I don't know how this is possible, but it shows shellStartup even though I had setting command

[karthiknadig]

WSL has 3 layers of settings User, Remote and workspace. Since wow support the activation setting at machine level only, there are two possible locations user and remote. Remote takes precedence over user.

[anthonykim1]

GlobalRemoteValue is undefined:

Maybe since its machine level , the remote setting doesnt get picked up.

[eleanorjboyd]

@karthiknadig would we want to scope this to window for remote scenarios? Since its scoped to machine right now I don't thinkkk it will then work in this remote case.