Bug Report - Font Ligatures interact with the shell prompt

[tensor-programming]

Environment

Windows 1903
Fira Code with Font Ligatures enabled

Steps to reproduce

Use a font with font ligatures and type - or = as your first character.

Expected behavior

I would expect the prompt not to interact with the characters. In c:\projects\> the > symbol should not connect with any font ligatures.

Actual behavior

The > symbol combines to create font ligatures.

The behavior is shown in the below images:

[mdtauk]

The Prompt should really be self contained. Maybe the settings screen should provide a visual way to choose your own prompt, if you wanted to use CharacterMap to insert a character, or a ligature sequence that wont combine with characters after it.

[tensor-programming]

Yes, this is what I am thinking as well. Decoupling the prompt from the inputted text to allow for different options. Then maybe custom prompts would also be possible.

In WSL at least there is a space between the prompt and the input so Ligatures are not possible. However, in both powershell and cmd it seems that they are.

[HBelusca]

Would inserting an (invisible) zero-width unicode space character after the end of the prompt fix the problem?

[tensor-programming]

You could fix the problem with a break character of any kind. Ligatures are combinations of unicode characters to build symbols and they are a part of the font.

[glen-84]

Duplicate of #514.