Closed stevehjohn closed 1 year ago
Update,
Changing the profile.ps1 script to use an escaped version of the character seems to have solved it.
Microsoft.PowerShell.Utility\Write-Host "`n$([char]0x03BB) " -NoNewLine -ForegroundColor "DarkGray"
Bit odd how the previous version worked on my other machines, but hey.
Microsoft.PowerShell.Utility\Write-Host "`nλ " -NoNewLine -ForegroundColor "DarkGray"
I'll leave this open for now so that you see it and are aware of the solution, but feel free to close it then.
Thanks,
Steve.
This is about Cmder, not about ConEmu.
@stevehjohn It looks like at some point the file(s) containing the lambda character was modified and/or saved as a non-UTF8 file, which then broke the character encoding and corrupted the lambda character. It's not a problem in Cmder, it's a problem in some configuration that happened locally after the installation. The character encoding in a file must be preserved in order for Unicode characters to work as intended.
This can be closed.
Sorry to revive this issue, but this is stated in the beginning of the file:
# NOTE: This file must be saved using UTF-8 with BOM encoding for the prompt symbol to work correctly.
If it's not, then the character encoding won't work correctly and as an alternative, you can choose to use the escaped sequence.
Versions
ConEmu build: 221278 stable x64 OS version: Windows 11 arm64 25276 Used shell version (Far Manager, git-bash, cmd, powershell, cygwin, whatever): cmder
Problem description
Hi,
I am unable to get ConEmu to show a unicode character prompt correctly. I have looked in open and closed issues and done much Googling, but cannot find a solution.
Sorry to add to your issue list.
Steve.
Steps to reproduce
Actual results
Expected results