237dmitry

> That is, both the following work ``` git log b `-- c ``` and ``` git log b - c ``` returned the same result


> and the Out-String solves the problem Yes, `null` in output, converting to string solves the problem: ``` Get-Content file.json -Raw | ConvertFrom-Json | ConvertTo-Json ```

> Read & Write Blank (`""`) If you mean double quotes: cmd.exe ``` > set blank="" > set blank blank="" ``` pwsh.exe ``` $ [environment]::SetEnvironmentVariable('blank','""',0) $ gi env:blank Name Value...

I think that PSReadline should understand `$PSStyle.OutputRendering = "PlainText"`, since unlike `NO_COLOR` it is cross-platform.

`NO_COLOR` is the first for syntax like `ENV=value command` And it does not work with aliases like `alias ls="ls --color"`

> I am not sure what you mean. I meant that this variable is not for global use so that the terminal becomes completely monochrome, but for launching individual utilities....

That's why we need to target pwsh so that the core and modules understand each other. To prevent PSReadline from being colorful when $PSStyle.OutputRendering is set to "PlainText". This is...

> I can't set the colours in Set-PSReadlineOption because they are not static, Base 16 console colors are not absolute, and they depend on terminal settings. Just enter in different...

> So when on a yellow background, it gave white text You have to configure terminal  ```powershell function set-mono { $PSStyle.OutputRendering = "PlainText" Set-PSReadlineOption -Color @{ Command...