cjk USE flag says it is for: Adds support for Multi-byte character languages (Chinese, Japanese, Korean) Since vim has a module to enable multibyte character support (unicode) this seems the logical flag to use, at the moment. About to file another bug that we need a USE flag for specific multibyte/unicode support and maybe respecify/deprecate cjk. Will add that bug ID shortly. Reproducible: Always Steps to Reproduce:
bug 26561 has been added requesting a clearer flag.
Atm, since vim ebuilds enable multibyte support by default (except vim-core), you mean we should turn off multibyte support if you don't have cjk in your USE flag?
It just seemed helpful to have the option, since it *is* a vim compile parameter. Perhaps make it a negative USE flag, to simply allow disabling. Really, what'd be nice is if the default vimrc also got modified if some sort of multibyte USE flag was enabled. Would also add a set encoding=(utf-8, or possibly something based on localization info)
Why would you want to disable unicode and multibyte support in vim? AFAIK there are no negative effects from having multibyte support there - hence the fact it is default, and I'm interested in why you'd want to swithch it off.
If you can state a good reason for turning off multibyte support in vim, please reopen this bug. At the moment, it doesn't seem worthwhile to me. I suspect some people appreciate the multibyte support who don't use cjk.
