Szymon Osiecki

I had the same problem and miniconda reinstallation solved it. Not quite innovative and profound solution but it worked. Seems like some broken dependencies in existing base environment.

> I had the same problem and miniconda reinstallation solved it. Not quite innovative and profound solution but it worked. Seems like some broken dependencies in existing base environment. I've...

So I've tried to copy pwsh.dll to script path, and got the error: ``` You must install .NET to run this application. App: /opt/microsoft/powershell/7/pwsh Architecture: x64 App host version: 7.0.0...

> Create a symbolic link to pwsh.dll in the directory that is in $PATH I've crated symlink with `ln -s /opt/microsoft/powershell/7/pwsh.dll /usr/bin/pwsh.dll` command, but it didn't help. Throws the same...

> Check if pwsh is executable. In 7.3.0 I did `chmod +x pwsh` Come on, how would pwsh work otherwise? Everything is working fine, when I'm using PowerShell directly, it's...

> > Come on, how would pwsh work otherwise? > > I deleted the post almost immediately, but you managed to read it. )) I was misled that in [powershell-7.3.0-linux-x64.tar.gz](https://github.com/PowerShell/PowerShell/releases/download/v7.3.0/powershell-7.3.0-linux-x64.tar.gz)...

> Just to give full solution, to call it with `-NoProfile` parameter, you need to add `-S/--split-string` parameter to env. Working shebang would look like this: ```sh #!/usr/bin/env -S pwsh...

Yes, please fix this. It's hard to recognize if you're working on a remote without it. It's much easier on original theme, when the indicator is green.