On 09/07/09 08:52, Aleksey wrote:
>
>> Make sure your 'fileencodings' option (plural) starts with "ucs-bom".
------------------------------------------^^^^^^
>
>> IIUC, even if 'fileencodings' doesn't work for quickfix error files,
>> setting LC_MESSAGES should be enough (LANG is used as a default for any
>> LC_<something> which is unset, or LC_ALL if present overrides any other
>> LC_* even if present). Maybe even just using ":language messages en-US"
>> or ":lang mess C" near the top of your vimrc could be enough.
>>
>> Best regards,
>> Tony.
>> --
>> hundred-and-one symptoms of being an internet addict:
>> 66. You create a homepage with the impression to cure the afflicted...but
>> your hidden agenda is to receive more e-mail.
>
> Thanks for your answer.
>
> fileencoding already had 'ucs-bom' in its start, so it didnt' help.

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 encoding used on disk for one file at a time. With
s, it's the heuristics to find what to use when opening an existing file.

> I also have :language messages C, so it didn't help either.
> I didn't quite understand what you wrote about LC_ stuff, because I
> lack even basic knowledge, but does it mean my solution with setting
> LANG=en_US is fine?

yeah, sure.

>
> Reading docs for VIM 7.2 (:help quickfix) I found the following
> paragraph:
> When 'encoding' differs from the locale, the error messages may
> have a
> different encoding from what Vim is using. To convert the
> messages you can
> use this code:
> function QfMakeConv()
> let qflist = getqflist()
> for i in qflist
> let i.text = iconv(i.text, "cp936", "utf-8")
> endfor
> call setqflist(qflist)
> endfunction
>
> au QuickfixCmdPost make call QfMakeConv()
>
> I've tried putting this to .vimrc replacing "cp936" with ucs-bom, but
> not sure if that was right. It didn't change anything.

no, iconv doesn't know about ucs-bom.

>
> I don't think this problem is worth of Bram's attention since it's not
> really wide-spread and the workaround is available.

How can one know how widespread it is? Sounds like the age-old "Nobody
uses it" used without proof by developers of some applications (not by
Bram) when speaking of a feature they want to remove because they don't
use it themselves and they don't want to support it.

OK, so IIUC the problem seems to be: When a compiler errorfile starts
with a BOM, Vim doesn't know how to handle it. I'm not sure if there's
an 'errorfile' setting allowing to get over it because I've never looked
into that option myself.


Best regards,
Tony.
--
"Benson, you are so free of the ravages of intelligence"
-- Time Bandits

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_multibyte" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---