Dirk MG Seynhaeve

I had a similar problem, as I was using this in all my scripts: ``` cat

I see, I found this [bug report](https://github.com/tree-sitter/tree-sitter-bash/issues/69) indeed, and voted it up... I am a little surprised that not more people run into this: the true power of a Bash...

I don't mind formatting depending on the shell-type. But the more I think about it, the more I would object to "options" to steer the formatting in the desired direction....

I am not sure this should be an option, I think it is normal, expected behavior that the code application inherits all the environment variables from the calling shell/environment...

I have installed the Perl::LanguageServer in my local::lib. When using the local::lib appropriately, it will updated your PERL5LIB environment variable to include the location of any libraries you installed there....

I can reproduce this error when: * I install `Perl::LanguageServer` with one version of Perl (e.g. Perl 5.30.3). * Run VS Code with a different version of Perl (e.g. Perl...

Even the relevant environment variables are dropped (e.g. PERL5LIB)... I tried to fix this by including this in my user `settings.json`: ```json "perl.perlInc": [ "${env:PERL5LIB}", ], ``` However, this notation...

Doesn't the Perl::LanguageServer just inherit the environment that it is invoked in? As far as I know, VS Code does know all the environment variables (you can even access them...

I tested what could become a workaround: In my settings file, I just set the environment variables: ``` "env": [ "PATH", "${env:PATH}", ], ``` The challenge is that our Perl...

I replaced `code` with `mycode`. 1. `mycode` will take a `.code-workspace` file, and update it: environment definitions marked by anchors get replaced by the "current environment". 2. Then the actual...