Bram Moolenaar wrote:
> Charles Campbell wrote:
>
>> Tony Mechelynck wrote:
>>> In Bitstream Vera Sans Mono 8 in gvim 8.0.600 for GTK3 (which I just
>>> made using "make reconfig" after an update of the python2, python3 and
>>> IIRC lua packages), U+20F0 is present in the buffer and gvim
>>>
BPJ wrote:
>
>
> Den 22 maj 2017 21:32 skrev "Charles E Campbell"
> >:
>
> Tony Mechelynck wrote:
> > In Bitstream Vera Sans Mono 8 in gvim 8.0.600 for GTK3 (which I just
> > made using "make reconfig" after an update of the
On Tuesday, May 23, 2017 at 4:35:19 AM UTC-5, Bram Moolenaar wrote:
>
> I suspect the glyph draws pixels outside of the character cell. Vim then
> erases them when drawing another character.
Would the 'linespace' option help, if this is the case?
--
--
You received this message from the
Charles Campbell wrote:
> Tony Mechelynck wrote:
> > In Bitstream Vera Sans Mono 8 in gvim 8.0.600 for GTK3 (which I just
> > made using "make reconfig" after an update of the python2, python3 and
> > IIRC lua packages), U+20F0 is present in the buffer and gvim
> > recognises it as a composing
Den 22 maj 2017 21:32 skrev "Charles E Campbell" :
Tony Mechelynck wrote:
> In Bitstream Vera Sans Mono 8 in gvim 8.0.600 for GTK3 (which I just
> made using "make reconfig" after an update of the python2, python3 and
> IIRC lua packages), U+20F0 is present in the
Tony Mechelynck wrote:
> In Bitstream Vera Sans Mono 8 in gvim 8.0.600 for GTK3 (which I just
> made using "make reconfig" after an update of the python2, python3 and
> IIRC lua packages), U+20F0 is present in the buffer and gvim
> recognises it as a composing character, but its display is easy to
In Bitstream Vera Sans Mono 8 in gvim 8.0.600 for GTK3 (which I just
made using "make reconfig" after an update of the python2, python3 and
IIRC lua packages), U+20F0 is present in the buffer and gvim
recognises it as a composing character, but its display is easy to
miss: AFAICT only 3 pixels are
Charles E Campbell wrote:
> Hello:
>
> I had been using a space (hex: 32) followed by a composing character
> (hex: 20f0) to get a superscript asterisk. I no longer see the
> "superscript" asterisk.
>
> * I did an o/s upgrade in the past 6 months or so, and so that could be
> why the "superscript
Hello:
I had been using a space (hex: 32) followed by a composing character
(hex: 20f0) to get a superscript asterisk. I no longer see the
"superscript" asterisk.
* I did an o/s upgrade in the past 6 months or so, and so that could be
why the "superscript asterisk" is no longer visible
*