tags:

views:

162

answers:

3

I'm trying to get the following into my .vimrc

" Use the same symbols as TextMate for tabstops and EOLs
set listchars=tab:▸\ ,eol:¬

Those lines are from here are worked perfectly in vim 7.2 I recently compiled and installed vim 7.3 and now those characters aren't understood by vim. Also: Ctrl+V then U in insert doesn't let me insert any characters, it just seems to ignore that.

Any ideas?

This is what I see: set listchars=tab:�~V�\ ,eol:¬

+1  A: 

Do you need a

scriptencoding utf-8

or whatever encoding your .vimrc is actually in?

Aristotle Pagaltzis
Also, check the values of `encoding`, `termencoding`, `fileencoding` options. Ensure that when you are editing `.vimrc` all of them are set to `utf-8`.
ib
I've added it and it still doesn't work. How do I check the value of those other options?
Sandro
You can see the value of any option by adding a ? after the set command. ie :set encoding?
Tassos
Woah weird! Apparently the "encoding" option is not supported. I typed ":set encoding?" and that's the error that I got.
Sandro
You must have a version of vim compiled with +multi_byte. The vim version must be B (Big), H (Huge) or a manually compiled with the +multi_byte flag. Check your build flags via :version
Peter Rincker
Yes! This ended up being the problem.
Sandro
A: 

I have the following in my .vimrc

scriptencoding utf-8
set encoding=utf-8

and that in my .gvimrc

set listchars=trail:·,precedes:«,extends:»,eol:↲,tab:▸\ 

and works fine(notice there is a space after the ▸\ ).

Tassos
I've added that and nothing...
Sandro
+1  A: 

You need to compile vim with multi-byte support.

The easiest way to do this is to run

./configure --with-features=big
make

This will build vim with the correct support.

You can verify that it was compiled correctly with

:version

in vim or by running

vim --version

and looking for +multi_byte. If it says -multi_byte it will not work.

Alan Geleynse
You nailed it! Awesome! Thank you, thank you, THANK YOU!
Sandro