Hi,
On Mi, 14 Sep 2016, manuelschiller.pimail via vim_dev wrote:
>
> let g:gtk_nocache=[0x00000000, 0xfc00ffff, 0xf8000001, 0x78000001]
>
> This contains a bitmap for each character < 128, which has the
> corresponding bit set if the glyph cache is to be bypassed (which in
> turn enables ligatures). The default is no ligatures, unless people
> set something like above in their .vimrc. With this slightly more
> sophisticated patch, people have the option to enable/disable certain
> ligatures by routing the corresponding characters through the cache
> (or not) without recompiling, if they so prefer.
>
> Comments remain welcome!
I appreciate your effort you put into this. But for the hell of it, I
can't understand how the values inside g:gtk_nocache are supposed to
work. Can you please describe more in detail, what each value stands
for?
I am afraid this needs some documentation and possibly a different
format. We don't have something similar like this. Perhaps a new type
for the 'renderoptions'?
Best,
Christian
--
Ich habe etliche mal bemerkt, daß ich Kopf-Weh bekam, wenn ich mich
lange in einem Hohl-Spiegel betrachtete.
-- Georg Christoph Lichtenberg
--
--
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 vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
