big with windows codepage 65001 (UTF-8)
78 views
Skip to first unread message
klo uo
Feb 26, 2016, 6:45:38 AM2/26/16
to v...@vim.org
Hi,
on Windows I've set my default code page to 65001 (UTF-8)
This is how vim looks like:
If I change code page to some other, like `chcp 866` if works as expected.
========================================
> vim --version
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Aug 10 2013 14:33:40)
MS-Windows 32-bit console version
Compiled by mool@tororo
Big version without GUI. Features included (+) or not (-):
+arabic +ex_extra -mouseshape +tag_binary
+autocmd +extra_search +multi_byte +tag_old_static
-balloon_eval +farsi +multi_lang -tag_any_white
-browse +file_in_path -mzscheme -tcl
++builtin_terms +find_in_path -netbeans_intg -tgetent
+byte_offset +float +path_extra -termresponse
+cindent +folding -perl +textobjects
+clientserver -footer +persistent_undo +title
+clipboard +gettext/dyn -postscript -toolbar
+cmdline_compl -hangul_input +printer +user_commands
+cmdline_hist +iconv/dyn -profile +vertsplit
+cmdline_info +insert_expand -python +virtualedit
+comments +jumplist -python3 +visual
+conceal +keymap +quickfix +visualextra
+cryptv +langmap +reltime +viminfo
+cscope +libcall +rightleft +vreplace
+cursorbind +linebreak -ruby +wildignore
+cursorshape +lispindent +scrollbind +wildmenu
+dialog_con +listcmds +signs +windows
+diff +localmap +smartindent +writebackup
+digraphs -lua -sniff -xfontset
-dnd +menu +startuptime -xim
-ebcdic +mksession +statusline -xterm_save
+emacs_tags +modify_fname -sun_workshop -xpm_w32
+eval +mouse +syntax
system vimrc file: "$VIM\vimrc"
user vimrc file: "$HOME\_vimrc"
2nd user vimrc file: "$HOME\vimfiles\vimrc"
3rd user vimrc file: "$VIM\_vimrc"
user exrc file: "$HOME\_exrc"
2nd user exrc file: "$VIM\_exrc"
Compilation: cl -c /W3 /nologo -I. -Iproto -DHAVE_PATHDEF -DWIN32 -DFEAT_CSCOPE -DWINVER=0x0400 -D_WIN32_WINNT=0x0400 /Fo.\ObjCi386/ /Ox /GL -DNDEBUG /Zl /MT -DDYNAMIC_ICONV -DDYNAMIC_GETTEXT -DFEAT_BIG /Fd.\ObjCi386/ /Zi
Linking: link /RELEASE /nologo /subsystem:console /LTCG:STATUS oldnames.lib kernel32.lib advapi32.lib shell32.lib gdi32.lib comdlg32.lib ole32.lib uuid.lib /machine:i386 /nodefaultlib libcmt.lib user32.lib /PDB:vim.pdb -debug
========================================
Ben Fritz
Feb 26, 2016, 10:29:53 AM2/26/16
to vim_use, v...@vim.org
On Friday, February 26, 2016 at 5:45:38 AM UTC-6, klo uo wrote:
> Hi,
>
>
> on Windows I've set my default code page to 65001 (UTF-8)
>
>
> This is how vim looks like:
>
>
>
>
>
> Hi,
>
>
> on Windows I've set my default code page to 65001 (UTF-8)
>
>
> This is how vim looks like:
>
>
>
>
>
> If I change code page to some other, like `chcp 866` if works as expected.
>
>
Works fine, for me.
>
>
What is your 'termencoding' setting after launching Vim in this way (if you can see that)? It should match (i.e. it should be cp65001).
Ken Takata
Feb 26, 2016, 5:29:32 PM2/26/16
to vim_use, v...@vim.org
Hi,
2016/2/26 Fri 20:45:38 UTC+9 klo uo wrote:
> Hi,
>
>
> on Windows I've set my default code page to 65001 (UTF-8)
>
>
> This is how vim looks like:
>
>
>
>
>
Try gvim74-1024.exe from http://www.vim.org/download.php#pc .
Old vim.exe needs to be set 'termencoding' properly when you change the codepage
(or 'encoding'). However recent vim.exe doesn't use 'termencoding'.
Regards,
Ken Takata
2016/2/26 Fri 20:45:38 UTC+9 klo uo wrote:
> Hi,
>
>
> on Windows I've set my default code page to 65001 (UTF-8)
>
>
> This is how vim looks like:
>
>
>
>
>
> If I change code page to some other, like `chcp 866` if works as expected.
Your vim.exe seems old.
Try gvim74-1024.exe from http://www.vim.org/download.php#pc .
Old vim.exe needs to be set 'termencoding' properly when you change the codepage
(or 'encoding'). However recent vim.exe doesn't use 'termencoding'.
Regards,
Ken Takata
Ben Fritz
Feb 26, 2016, 7:05:32 PM2/26/16
to vim_use, v...@vim.org
On Friday, February 26, 2016 at 4:29:32 PM UTC-6, Ken Takata wrote:
> However recent vim.exe doesn't use 'termencoding'.
>
> However recent vim.exe doesn't use 'termencoding'.
>
Woah, when did that happen?
klo uo
Feb 26, 2016, 11:48:51 PM2/26/16
to vim_use, v...@vim.org
On Friday, February 26, 2016 at 4:29:53 PM UTC+1, Ben Fritz wrote:
>
> Works fine, for me.
>
>
> What is your 'termencoding' setting after launching Vim in this way (if you can see that)? It should match (i.e. it should be cp65001).
>
> Works fine, for me.
>
>
> What is your 'termencoding' setting after launching Vim in this way (if you can see that)? It should match (i.e. it should be cp65001).
Thanks. I've set encoding to utf8 in my vimrc and it is fine now.
Ken Takata
Feb 27, 2016, 12:34:34 AM2/27/16
to vim_use, v...@vim.org
Hi Ben,
It's 7.4.852.
Now vim.exe uses Unicode API.
Regards,
Ken Takata
Reply all
Reply to author
Forward
0 new messages