On 21/03/09 00:39, Andreas Klein wrote:
>
> Hi Björn,
>
> * bjorn.winckler wrote:
>> Thanks. Unfortunately I cannot reproduce the problem: I've tried
>> typing "<<" followed by space, text, whatever...nothing weird
>> happens. Same story with "(" and "&&". Does the problem occur
>> regardless what type of file you are editing? I just opened MacVim
>> with a blank window and started hitting keys...maybe that doesn't
>> trigger the bug?
>>
>> Have you tried disabling your .[g]vimrc and plugins to see some
>> settings in there may be causing this problem (e.g. use the "-u NONE"
>> switch or temporarily rename .vim, .vimrc, .gvimrc)?
>
> I moved my .vim and my .vimrc away and started vim with -u NONE.
> Unfortunately this did not fix the problem.
>
> It happens regardless of which file type I edit. And it does not
> happen deterministically. So when I type "==" sometimes this \194 gets
> inserted sometimes not.
>
> Here is a hexdump of a file I creatad with vim -u NONE on my system:
>
> 0000000: 2626 c2a0 0a3d 3d20 0a3c 3c20 0a&&...== .<< .
>
> You see, strange characters get inserted when I type "&&".
>
> I found this behaviour both in MacVim and the vim I compiled out of
> MacPorts.
>
What is 'encoding' set to? (Also 'fileencoding' for the above file.)
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.
Best regards,
Tony.
--
You can lead a whore to Vasser, but you can't make her think.
-- Frederick B. Artz
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
