Tony Mechelynck, 03.03.2009: > > On 03/03/09 06:40, James Vega wrote: > > On Tue, Mar 03, 2009 at 03:32:45AM +0100, Tony Mechelynck wrote: > >> 2) Vim compiled with the --disable-multibyte configure option cannot use > >> UTF-8, or any other multibyte encoding; in fact it doesn't even accept > >> the 'encoding' option as valid. > > > > Is there a reason to allow building Vim without multibyte support? > > Always having multibyte support would make the code simpler/smaller. > > With +multi_byte is always bigger than -multi_byte: one reason could be > making the Vim binary really "lean and mean". Personally I keep two Vim > builds on this computer: a Huge build named vim, with GTK2/Gnome2 GUI > (and +multi_byte), used via softlinks for most possible executable > names, and a Tiny build named vi (with no GUI and -multi_byte).
Why the tiny build without multibyte? Is this only a fallback in case of system problems, when root has to edit config files, where you know, they don't contain multibyte characters? Markus --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
