----- Original Message -----
From: Pavel "ShadoW" Dvo??k
To: Tony Mechelynck
Sent: Sunday, August 21, 2005 11:02 PM
Subject: Re: Vim windows-1250 encoding bug
> OK, I already understand that autocommand thing :)).
> But I have all in default setting.
> Problem still remains, when I use :e ++enc=cp1250 <file>.
> And I don't have problem with OPEN files in cp-1250, but in
> VIM is bug, that doesn't set right encoding at SWITCH from
> one buffer to another. Do you understand me? (Sorry again
> about my english, I never learned thit language :(.)
Well, what exactly are you doing, and what are you seeing (which exact
commands and which exact symptoms)? By being as precise as possible, you
make it easier to either reproduce the bug or spot the false maneuver.
Are you having the same problem when starting vim with no startup scripts as
gvim -N -u NONE
1. please respond on the mailing list as long as you are not straying
off-topic. You can do that by using "Reply to all" rather than "Reply to
2. please use plain text rather than HTML. (The Vim lists reject HTML