237dmitry

> but PowerShell itself does! It seems not... 

> Eg from bash.. What is the difference? Look at screenshot once more -- NO_COLOR has been exported before terminal and pwsh started Ok, new screenshot: 

With `-NoProfile` is `PlainText` But is it even possible to rely on personal settings in this matter? I think not. Otherwise, it turns out that the option with `NO_COLOR` is...

> Let me try to summarize: - Without unloading `PSReadline`, works with any configuration: ``` $PSStyle.OutputRendering = "PlainText" Set-PSReadlineOption -Colors @{ Command = "`e[37m" Comment = "`e[37m" ContinuationPrompt = "`e[37m"...

Intersting, does this work? ``` del temp:\1.txt ``` PS. Use utf-8 as system wide locale, 2024 already.

> It works in CMD. ``` The filename, directory name, or volume label syntax is incorrect. ``` I am about pwsh

Ok, I thought it might be possible using PSDrive `temp:` this would work not `temp\1.txt` but `temp:\1.txt` ``` PS > Get-PSDrive -Name Temp Name Used (GB) Free (GB) Provider Root...

> When I ran it on 7.4.1 again I got a ghost 'm' appended after the cursor I did not get https://github.com/PowerShell/PowerShell/assets/78153320/cffa85e4-687a-4351-98f9-8beb1bf6db65 In 5.1 works as expected if unload PSReadline...

> The ghost "m" in PowerShell Core indeed comes from the command history I think this is an artifact from PSReadline colors. I ran into this problem when writing my...

Configure `$PSStyle` For example white directory color: ``` $PSStyle.FileInfo.Directory = "`e[38;2;255;255;255m" ```