I tracked the error: it is happening because of the vimspell plugin.
When I deactivate it (let loaded_vimspell = 1), everything is back to
normal.
How should I proceed? Should I contact the vimspell developer?
Thanks a lot!
PS: I was writing an answer with some more info before I found the
problem, I post it here anyway.
Ben: Yes, it must be due to the plugins (i.e. it works fine with "-N -u
NONE -i NONE").
It happens with all buffers.
Tim:
vim 7.3, included patches 1-154 (should this be reported as 7.3.154?).
Running on Ubuntu 11.10 64 bit.
Error happens both on gvim and vi.
The final file has as weird characters *only* the ones added with ".".
The xxd experiment confirms, ie, normal blanks are "20" and the weird
characters as "62c2".
On Thu 17 Nov 2011 05:14:06 PM EET, Tim Chase wrote:
> On 11/17/11 07:50, Ben Fritz wrote:
>> On Nov 17, 3:56 am, Sergio Losilla<loxim...@gmail.com>
>> wrote:
>>> A while ago, I noticed that when I use "." to repeat an
>>> insert, the spaces get replaced by not signs (
>>> ,¬,¬). For instance, the following sequence of
>>> keystrokes: "aa b c<ESC>." produces the following text: "a b
>>> ca b c".
>>>
>>> I checked that the characters are actually those (they are
>>> saved to file), not just a visual representation of spaces.
>>>
>>> I looked at the ". register, and the weird characters were
>>> already there.
>>
>> What version of Vim are you running? Any plugins you know may
>> affect the '.' command? Does it happen also when running Vim
>> without your plugins or mapping, e.g. "gvim -N -u NONE -i
>> NONE"? All buffers, or only buffers with a certain filetype?
>
> Included in the "what version of Vim", it would be helpful not only to
> have the version number ("7.2.123"), but how you're running it and the
> platform: Win32 vs. Linux/Mac/BSD, gvim vs. console vim.
>
> Also, when you say that the final file has the weird characters, is it
> *all* the spaces, or just the ones added with "."? It might also be
> helpful to epeat your experiment of "aa b c<esc>." then pipe your
> contents through xxd to see what gets written where:
>
> :%! xxd
>
> which should change your buffer contents to something like
>
> 0000000: 6120 6220 6361 ac62 ac63 0a a b ca.b.c.
>
> or
>
> 0000000: 61ac 62ac 6361 ac62 ac63 0a a.b.ca.b.c.
>
>
> I agree with Ben that this is highly non-standard behavior.
>
> -tim
>
>
>
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
No comments:
Post a Comment