Be sure to check the existing issues (both open and closed!), and make sure you are running the latest version of Guake.
For how to run the latest Guake in your computer, please refer to Install from source.
Describe the bug
https://github.com/microsoft/cascadia-code/releasesExpected behavior

Actual behavior

To Reproduce
Just type inside guake:
pwegrzynek@WegrzyNET:~$ echo "4+4=8"
4+4=8
pwegrzynek@WegrzyNET:~$ echo "4+4==8"
4+4==8
pwegrzynek@WegrzyNET:~$ echo "4+4===8"
4+4===8
pwegrzynek@WegrzyNET:~$
It seems that whenever Cascadia has the ability to join two or more chars, does not display anything, or display it wrong
For example:

Please run $ guake --support, and paste the results here. Don't put backticks (`) around it! The output already contains Markdown formatting. And make sure you run the command OUTSIDE the Guake.
pwegrzynek@WegrzyNET:~$ guake --support
[WARN] Unable to load the library libutempter !
[WARN] The
[WARN] libutempter.so.0: nie mo偶na otworzy膰 pliku obiektu dzielonego: Nie ma takiego pliku ani katalogu
Usage: main.py [options]
main.py: error: no such option: --support
VTE does not support ligatures, so you won't get those long or triple equal signs. Instead, you should get two or three separate = signs next to each other.
There used to be a bug as you describe, empty or incorrect glyphs showing up where the font defines a ligature. This was fixed in VTE version 0.52. Please make sure your Guake uses VTE 0.52 or newer.
Any plans for ligature support in Guake?
Most helpful comment
Any plans for ligature support in Guake?