You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Same setup (pwsh 7.5.0). With Cascadia font it works fine.
Trying the same setup using Cascadia Code results in the same result for me. As you can see, the => renders correctly in the screenshots below. I also updated pwsh to 7.5.0 and the problem remains. The same ligatures render correctly in the Windows Terminal.
Ligatures are now temporarily disabled while the cursor or the selection is within the ligature.
This isn't what's causing the problem here. Other ligatures render correctly with the same setup and cursor/selection placement, as seen in the screenshots attached. From my testing only ligatures starting with a pipe are affected, I haven't tested all of them, however.
The same text in a blank editor for reference. Both use the Fira Code Nerd Font in this example.
Sorry, I misunderstood the issue and I tried the ligature without starting a pipe.
Indeed I reproduced the issue, even if only |=== works fine, the rest of your examples are not a ligature here.
Does this issue occur when all extensions are disabled?: Yes/No
Steps to Reproduce:
terminal.integrated.fontLigatures.enabled
in the settings|== and |=== and |--- and |->
in the terminalI haven't tested this issue with different fonts and different shells.
The text was updated successfully, but these errors were encountered: