On 05/08/13 09:05, mattn wrote:
Hi Bram.
When enc=utf-8, vim pass the command arguments as utf-8 string on windows. Thus, :grep
doesn't work with multbyte string. If ACP is CP932 and type ":echo XXX" as
utf-8, vim calls:
cmd /c (echo XXX)
If XXX is 3 byte utf-8 string, windows command prompt treat the arguments like
"XXX)".
https://gist.github.com/mattn/6153332
Please check.
Thanks.
- Yasuhiro Matsumoto
1. What is 'encoding' set to if you start Vim with no vimrc?
vim -u NORC -N
2. When running normally, what is 'termencoding' set to? If it is the
empty string (which is the defaut) try using the code snippet from
http://vim.wikia.com/wiki/Working_with_Unicode and see if you get a
better result.
I'm assuming you're talking about Console Vim (vim.exe, if on Windows)
and not GUI Vim (aka gvim).
Best regards,
Tony.
--
Renning's Maxim:
Man is the highest animal. Man does the classifying.
--
--
You received this message from the "vim_dev" 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
---
You received this message because you are subscribed to the Google Groups "vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
