* Tony Mechelynck wrote:
>
> > 0000000: 2626 c2a0 0a3d 3d20 0a3c 3c20 0a&&...== .<< .
>
> What is 'encoding' set to? (Also 'fileencoding' for the above file.)
if has("multi_byte")
set encoding=utf-8
setglobal fileencoding=utf-8 bomb
set fileencodings=ucs-bom,utf-8,latin1
endif
I tried deleting these settings from my .vimrc which unfortunately did not
solve the problem.
My terminal is set to handle utf-8 and the screen running in it is also set to
utf-8.
> C2 A0 is UTF-8 representation of U+00A0 NO-BREAK SPACE. Otherwise 0x20
> is space and 0x0A is linefeed, both of which are rather "normal" in a
> text file. Does this ring a bell? I don't see anything in this dump that
> could be understood as \194.
As I see here 0xC2 corresponds to 194 which is an A with some fancy accent but
I may be mistaken here.
\194 is what gcc says when I try to compile a file with these characters in it.
Hmm maybe there is a way to work around these problems by automatically
deleting these characters when a file is saved?
I just don't know how to search for them in vim.
--
Best regards,
Andreas Klein
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
