Guake: Some characters are invisible with cascadia-code font

Created on 20 Sep 2019  路  2Comments  路  Source: Guake/guake

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

  1. Download Cascadia-code font from official repository:
    https://github.com/microsoft/cascadia-code/releases
  2. Install it
  3. Set it as font used within guake

Expected behavior

image

Actual behavior
image

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:

image


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 command will not work in guake !
[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

Most helpful comment

Any plans for ligature support in Guake?

All 2 comments

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?

Was this page helpful?
0 / 5 - 0 ratings