cmder: Cmder prompt/shortcuts broken in latest Windows build
Purpose of the issue
- Bug report (encountered problems/errors)
- Feature request (request for new functionality)
- Question
Version Information
- Cmder: Version 1.3.15.1010
- ConEmu: 19.10.12.0
Windows version: Windows 10 Build 20157 (pre-release)
Description of the issue
The latest Windows Insider build broke my cmder, and now I don’t get the lambda prompt, nor do the shortcuts work (Ctrl+R, Alt+Ctrl+U, etc.). I’d love to help you debug or run other builds.
I tried the latest release (1.13.15.1010) just to confirm, but I was using 1.3.14.982 before, and that’s broken as well.
Please let me know how I can help 😃 I’d love to get this fixed/root-caused.
An image of the current prompt:
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 30 (20 by maintainers)
Hey this might be related to another bug When using the current Version (1.3.16) the prompt for the powershell seems broken. Instead of a lambda it shows an λ.
This is not the case for powershell core or in earlier versions like 1.3.12. I tried to copy the default profile.ps1 from the 1.3.12 to 1.3.16 but that didn’t change anything.
EDIT: I updated the profile.ps1 script and replaced the λ symbol on line 71 with $([char]0x000003BB) and the lambda symbol now shows up again in powershell. This change doesn’t break powershell core and could be replacement.
@cmderdev/trusted-contributors Sorry for the (multi-year) delay, you should all have the permissions now