On Thursday, December 18, 2014 3:52:10 PM UTC-8, [email protected] wrote: > Hi, I'm trying to run gvim with a font that has ligatures for things like > "<=" or "->". Gvim starts up with this error: > > ** (gvim:817): CRITICAL **: ascii_glyph_table_init: assertion > 'gui.ascii_glyphs->num_glyphs == sizeof(ascii_chars)' failed > > After starting up, gvim displays garbage. Vim (not gvim) and everything else > like terminal works perfectly fine.
Let me guess...you're using the PragmataPro update of the same day? I experienced this as well. The code that makes the assertion is setting up a cached glyph table for ASCII characters. Unfortunately, the code works on the assumption that the number of characters fed into Pango necessarily results in the same number of glyphs out. This typeface collapses sequences of '??' and '<=>' into a single glyph, and these are both found in the ASCII cache input string. There was a related patch posted earlier this year (https://groups.google.com/d/topic/vim_dev/0sETSAwe5Wo/discussion) to only "optimize" ASCII characters in the alphanumeric range, but it would not solve your ligature issue, because sequences of '??' are still found in the input string. Bram suggested adding an option that could disable the optimization though, which is probably the safest/easiest way to resolve it quickly. -Chip -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
