DisposaBoy / GoSublime

A Golang plugin collection for SublimeText 3, providing code completion and other IDE-like features.
MIT License
3.42k stars 302 forks source link

Content-complete info display error #92

Closed GeertJohan closed 5 years ago

GeertJohan commented 12 years ago

So, I had this problem and got it fixed after a while, still reporting here. I don't know if this is something GoSublime should fix or SublimeText or maybe even Pango..

I"m using ST2+GoSublime quite a while now on multiple platforms. I recenty moved to Kubuntu 12.04 on desktop and laptop (Note the K for KDE). On these Kubuntu installs, I noticed that the specification given in the content-complete box (ctrl+space) was unreadable. It just showed these blocks (▯) on instead for each character. ▯indicates that the character can not be rendered by the font (correct me if I'm wrong).

Taking a look at the programs output I got these warnings: (st:5351): Pango-WARNING _: failed to create cairo scaled font, expect ugly output. the offending font is 'DejaVu Sans Mono Oblique 9.9990234375' (st:5351): Pango-WARNING _: font_face status is: no error has occurred (st:5351): Pango-WARNING **: scaled_font status is: out of memory

Doing some searches I found that the dejavu font was apparently missing. So I installed: sudo aptitude install ttf-dejavu ttf-dejavu-extra Then it worked again, the information is clearly readable again.

It seems that GoSublime (or ST, or Pango?) assumes the font is installed. I guess it's not being installed with Kubuntu 12.04, as I have (or rather: had) this on two different Kubuntu 12.04 machines. I have no clue how many people are affected by this. (I assume at least all Kubuntu 12.04 users). Neither do I know if this can be fixed, and where it should be fixed. But I hope this issue might help other uesrs, or get the ttf-dejavu and tff-dejavu-extra packages added to the dependencies list.

Thank for creating and maintaining GoSublime, you're doing a very good job! ~~GeertJohan

DisposaBoy commented 12 years ago

Thanks for the report. I marked it as sticky in-case anyone else stumbled upon the same issue. This is a ST2 issue. I'm not sure if it's a bug or not as I imagine most people would set their own font. The default, however it's picking it up has always been a little bit of an eyesore to me.