vim-multibyte at Yahoo! Groups

Re: ANSI<>UNICODE and reverse

John Beckett — Fri, 06 Nov 2009 02:23:00 GMT

... See discussion in vim_use http://groups.google.com/group/vim_use/browse_thread/thread/cc7e9076fa7d277d John

Re: ANSI<>UNICODE and reverse

winterTTr — Fri, 06 Nov 2009 00:54:58 GMT

... What's the value for the option "encoding" ? if the "encoding" is set to utf-8 when you don't set "fenc" , the file will open with the same encoding as

ANSI<>UNICODE and reverse

wintec — Thu, 05 Nov 2009 21:25:46 GMT

Hi all! I need to perform ANSI/UNICODE commands in my GVIM. I read many docs on the web about and I did set these: "------------------------------------------

Not a Vim announcement

Bram Moolenaar — Sun, 04 Oct 2009 13:19:07 GMT

Hello Vim users! Vim bug fixes are coming out one by one, not very exciting but essential maintenance. Keeps me busy. Nothing worth announcing though, that

Not a Vim announcement

Bram Moolenaar — Sun, 04 Oct 2009 13:18:56 GMT

Hello Vim users! Vim bug fixes are coming out one by one, not very exciting but essential maintenance. Keeps me busy. Nothing worth announcing though, that

Re: BOM in QuickFix window

Aleksey — Thu, 09 Jul 2009 10:11:41 GMT

On Jul 9, 1:51 pm, Tony Mechelynck ... Sorry, mistyped it. It's 'fileencodings' certainly, and 'ucs-bom' is the list. ... I

Re: BOM in QuickFix window

Tony Mechelynck — Thu, 09 Jul 2009 09:52:41 GMT

... should be 'fileencodings' with s at the end. There are two different options, with and without s, and they don't have the same meaning. Without s, it's the

Re: BOM in QuickFix window

Aleksey — Thu, 09 Jul 2009 06:52:54 GMT

... Thanks for your answer. fileencoding already had 'ucs-bom' in its start, so it didnt' help. I also have :language messages C, so it didn't help either. I

Re: BOM in QuickFix window

Tony Mechelynck — Thu, 09 Jul 2009 03:53:31 GMT

... Make sure your 'fileencodings' option (plural) starts with "ucs-bom". In that case, for editfiles at least (not sure about quickfix error files), Vim will

BOM in QuickFix window

Aleksey — Thu, 09 Jul 2009 01:54:29 GMT

Hi. I'm using few MONO apps (Nemerle compiler and COCO/R parser generator) through compiler plugins in VIM under Linux, and the problem is that they produce

Re: About line wrap when both English and Chinese Chars are present

Bram Moolenaar — Sun, 05 Jul 2009 10:41:55 GMT

KL wrote: [ Please mention your name ] ... Perhaps this code will help: http://vimgadgets.sourceforge.net/liblinebreak/ -- ERROR 047: Keyboard not found.

About line wrap when both English and Chinese Chars are present

KL — Sun, 05 Jul 2009 01:13:31 GMT

Hi, I hope this is the correct place to bring up this question. I love vim very much! But I think that Vim's localization is still not perfect.

Re: Failed to drag&drop-open a file with wide-chars in its filename

Tony Mechelynck — Wed, 24 Jun 2009 13:34:33 GMT

... Hm, NFKC and NFKD sometimes fuse slightly different glyphs into a single "normalized" form. For instance, NFKC(²) = 2, though both are (different) Latin1

Re: Failed to drag&drop-open a file with wide-chars in its filename

John (Eljay) Love-Jensen — Wed, 24 Jun 2009 13:33:02 GMT

Hi Björn, ... Drat, I cannot find the MSDN reference. Maybe my memory has failed me. NFKC is lossy. NFC is non-lossy. Perhaps you are remembering the

Re: Failed to drag&drop-open a file with wide-chars in its filename

björn — Wed, 24 Jun 2009 12:01:47 GMT

Hi Eljay, ... Thanks for clarifying that (and for the links!). ... I read that Windows uses NFKC. Have you got a reference for the claim that NFC is used? ...