search

flycutter-zfz / vim

Automatically exported from code.google.com/p/vim
0 stars 0 forks source link

% character not rendered properly all of a sudden #370

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
Not sure, it happened all of a sudden, but it is currently persistent so feel 
free to ask me to run any commands on my computer and will report it back here.

What is the expected output? What do you see instead?
The "%" character looks correct if I put the cursor on it, but when I move away 
I see the strange shape you see in the screenshot on the first line (after the 
backslash). Note that this is not a hiccup, I close vim and opened the file 
again.

What version of the product are you using? On what operating system?
$ vim -v
version 7.3.315

$ lsb_release -a
LSB 
Version:    :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics
-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
Distributor ID: CentOS
Description:    CentOS release 6.5 (Final)
Release:    6.5
Codename:   Final

Original issue reported on code.google.com by omar.oth...@booking.com on 10 Jun 2015 at 1:46

Attachments:

GoogleCodeExporter commented 9 years ago 
What does ":verbose set conceallevel? concealcursor? listchars?" say?

Original comment by fritzoph...@gmail.com on 10 Jun 2015 at 2:57

GoogleCodeExporter commented 9 years ago 
:verbose set conceallevel? concealcursor? listchars?
  conceallevel=0
  concealcursor=
  listchars=eol:$

Original comment by omar.oth...@booking.com on 10 Jun 2015 at 3:26

GoogleCodeExporter commented 9 years ago 
Is this gvim or terminal vim? Does it make a difference? If you turn syntax 
off, does it look correctly? Could this be a font issue (e.g. try in your gvim 
a different guifont setting or change your terminals font please).

Original comment by chrisbr...@googlemail.com on 10 Jun 2015 at 3:28

GoogleCodeExporter commented 9 years ago 
It is terminal vim, I don't have gvim installed. Changing the syntax 
highlighting had no effect, but changing the terminal font did! Now I'm 
confused, since I've been using the same terminal settings forever and it 
started to happen only today, so I thought a vim update did something wrong.

Sorry for disturbance, and thanks for the clever suggestion, Chris!

Original comment by omar.oth...@booking.com on 10 Jun 2015 at 3:36

GoogleCodeExporter commented 9 years ago 
(closing)

Original comment by chrisbr...@googlemail.com on 11 Jun 2015 at 10:28

GoogleCodeExporter commented 9 years ago 
Sounds like a corrupt font cache.  HTH.

Original comment by John.B.L...@gmail.com on 14 Jun 2015 at 10:00