Tony wrote:
> I'm not particularly in favour of keeping the ability to build without > +multi_byte (and/or without +multi_lang) except that my configure > arguments for the tiny build (which I build mostly as a sanity test > for "compilability" without bells and whistles, I don't really "use" > it) include an explicit --disable-multibyte. Will that: > - be treated as an error and cause "make" to stop then and there with > nonzero exit code? (IMHO not desirable) > - be treated as a comment? (IMHO better) > - cause auto/configure to issue a warning message but disregard that > particular --disable argument? (IMHO best: doesn't break backward > compatibility but warns the user that it is no longer possible to > disable that feature) Normally when a choice is removed the configure argument is removed. In this case we can keep it, but it won't have an effect. When it is used to enable multi-byte it's a no-op. When it is used to disable multi-byte we could indeed give an error. I'm actually thinking of first always enabling multi-byte, without changing the code yet, just in case someone runs into a problem. Not that many people will have seen the question on the mailing list. -- "Hit any key to continue" is very confusing when you have two keyboards. /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
