Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invisible = sign #162

Open
hauleth opened this issue Mar 29, 2016 · 23 comments
Open

Invisible = sign #162

hauleth opened this issue Mar 29, 2016 · 23 comments

Comments

@hauleth
Copy link

hauleth commented Mar 29, 2016

I am using Terminal GNOME 3.16.2 and when I am trying to use Fira Code 1.102 = sign (0x3d) is invisible.

zaznaczenie_457x56_018

@rahilwazir
Copy link

ping @tonsky

@tonsky
Copy link
Owner

tonsky commented Apr 15, 2016

Yeah, guys, I don’t have Gnome terminal to test. Have you considered a possibility there’s a bug in terminal itself? Because Fira Code works really well everywhere else

@rahilwazir
Copy link

rahilwazir commented Apr 18, 2016

@tonsky I have tested with several other fonts like

  • Hack
  • Ubuntu Mono
  • Source Code Pro
  • Andale
  • DejaVu
  • Droid Sans Mono

They are all working fine.

@tonsky
Copy link
Owner

tonsky commented Apr 18, 2016

Any specific sequence where = disappears?

On Mon, Apr 18, 2016 at 7:01 PM Rahil notifications@github.com wrote:

@tonsky https://github.com/tonsky I have tested with several other
fonts like Hack, Ubunt Mono, Source Code Pro, Andale, DejaVu, Droid Sans
Mono, they all working fine.


You are receiving this because you were mentioned.

Reply to this email directly or view it on GitHub
#162 (comment)

@rahilwazir
Copy link

rahilwazir commented Apr 18, 2016

@tonsky No, just type = anywhere in any sequence, it just displays as invisible.

@MadcapJake
Copy link

Gnome Terminal doesn't support ligatures so you should just use Fira Mono with Gnome Terminal.

@hauleth
Copy link
Author

hauleth commented Apr 18, 2016

I have been using FiraCode as it also provides other smaller or bigger changes to the font other than ligatures (ex. Powerline symbols)

Łukasz Jan Niemier

Dnia 18 kwi 2016 o godz. 18:10 Jake Russo notifications@github.com napisał(a):

Gnome Terminal doesn't support ligatures so you should just use Fira Mono with Gnome Terminal.


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

@KaelWD
Copy link

KaelWD commented Apr 22, 2016

Broken for me in phpstorm as well.

image

This is supposed to be

= == ===
- -- ---
!= !==

EDIT: Seems to be related to font size, this is at size 12 instead of 14:
image

@MadcapJake
Copy link

@KaelWD please open a separate issue, PHPStorm is a completely different implementation of ligatures to Gnome Terminal's (also your issue is different just in general).

@rahilwazir
Copy link

@KaelWD I'm confused?! Whats the issue?

@KaelWD
Copy link

KaelWD commented Apr 22, 2016

@MadcapJake Sorry, will do. It just seemed related because it's a similar problem (part or all of the = character not rendering).

@rahilwazir At size 14 (img 1), = and == display as a short and long dash respectively. At size 12 the spacing between the lines is off, most visible in !==.

@tonsky
Copy link
Owner

tonsky commented Apr 22, 2016

@KaelWD report to https://youtrack.jetbrains.com/issue/IDEA-127539

@hauleth @rahilwazir is it broken in Gnome terminal only or in all other linux apps as well. What font rendering setting are you using system-wide?

@rahilwazir
Copy link

@tonsky Only in Gnome Terminal.

Hinting: Maximum/Full
Antialiasing: RGBA

@ptkato
Copy link

ptkato commented May 27, 2016

It's also broken in Terminator, the '=' sign is gone and all other ligatures are messed up.

@topaxi
Copy link

topaxi commented Sep 20, 2016

This is an issue with libvte (the terminal library gnome-terminal, terminator and other terms use).

See here: https://bugzilla.gnome.org/show_bug.cgi?id=584160

@meskarune
Copy link

Also happens in termite terminal, which also uses libvte. So I just wanted to confirm.

@concatime
Copy link

concatime commented Nov 11, 2017

Any news? It seems that we're kinda stuck.
(Also had the issue with the = inside Termite, no matter which font is used)

@tonsky
Copy link
Owner

tonsky commented Nov 13, 2017

was this reported to libvte? maybe you should ask them to fix it?

@klummy
Copy link

klummy commented Nov 29, 2017

I think this is likely related to #247 since Gnome Terminal doesn't support ligatures

@Albert221
Copy link

I've also experienced this issue. I think that using Fira Mono as terminal font is a good way to avoid this problem, but this should be definitely fixed

@kdrag0n
Copy link

kdrag0n commented Feb 20, 2018

Having this issue in every libvte terminal I've tried as well. Fira Mono works fine. Not only is = broken, </a> is broken and displays /b with the <=> overlapping it. Examples:
image </b>

image <a href="test"> <a></b>

@cben
Copy link

cben commented Nov 6, 2018

FWIW, I saw weird char replacement issues in GNOME Terminal 3.28.2 using VTE 0.52.2 (on fod, in only some Fira Code variants:

  • only in Fira Code Retina, | U+007C VERTICAL LINE displayed exactly as ^
    captura de pantalla de 2018-11-05 23-14-07

  • only in Fira Code Bold Italic, | U+007C VERTICAL LINE displayed as &, and some other chars +^ displayed as ...
    captura de pantalla de 2018-11-05 23-14-51

But after playing with antialising settings back and forth, things changed (eg. now retina is good but bold and italic bold show | as &), so I guess these are not specifically these fonts and chars, but some kind of font cache issues... (?)

@imflash217
Copy link

Same issue even now on some ubuntu installations (on both Guake, Gnome Terminal).
Fira Mono works fine though.

Losangelosgenetics pushed a commit to Losangelosgenetics/FiraCode that referenced this issue Mar 12, 2020
…uction_code, r=olleolleolle

Suppress deprecation warnings in production code

This PR suppresses the following Ruby warnings in production codes.

- ⚠️ `warning: URI.unescape is obsolete`
- ⚠️ `warning: URI.regexp is obsolete`
- ⚠️ `warning: instance variable @properties not initialized`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests