Hello,
* On Wed, May 17, 2006 at 08:13:05PM +0200, A.J.Mechelynck [EMAIL PROTECTED]
wrote:
The problem has existed for a long time. The iconv() workaround
works correctly with vim 7.0.012 on linux, but not with vim 7.0.000
(default win32 build) on windows.
Do you have +iconv or
Dnia wtorek, 16 maja 2006 23:35, Luc Hermitte napisał:
The problem has existed for a long time. The iconv() workaround works
correctly with vim 7.0.012 on linux, but not with vim 7.0.000 (default
win32 build) on windows.
Do you have +iconv or +iconv/dyn in :version? For better work with
Yakov Lerner [EMAIL PROTECTED] wrote:
On 5/17/06, Luc Hermitte [EMAIL PROTECTED] wrote:
I have a problem with an old hack that works fine in latin1, but starts
to cause problems in UTF-8.
[...]
What is quite odd is that I have a workaround on Linux (by calling
iconv()) which has no,
Mikolaj Machowski [EMAIL PROTECTED] wrote:
Dnia wtorek, 16 maja 2006 23:35, Luc Hermitte napisa³:
The problem has existed for a long time. The iconv() workaround works
correctly with vim 7.0.012 on linux, but not with vim 7.0.000 (default
win32 build) on windows.
Do you have +iconv or
Dnia środa, 17 maja 2006 18:34, [EMAIL PROTECTED] napisał:
Mikolaj Machowski [EMAIL PROTECTED] wrote:
Dnia wtorek, 16 maja 2006 23:35, Luc Hermitte napisa?:
The problem has existed for a long time. The iconv() workaround
works correctly with vim 7.0.012 on linux, but not with vim 7.0.000
Hello,
I have a problem with an old hack that works fine in latin1, but starts
to cause problems in UTF-8.
The hack helps to replace activation key-sequences from i-mappings with
their mapped value, which are actually calls to script-local functions.
What is quite odd is that I have a
