On Thu, Feb 14, 2013 at 12:54 PM, Christian Brabandt wrote: >> Question is, if you run into a problem, how do you know you have to turn >> off that option? If syntax highlighting is off it might be obvious, but >> when some plugins behave badly you might not have a clue. > > Anybody that uses such an option should be aware, that this can have > consequences. So I would expect the first thing to do when one notices > something strange to turn that option off.
I think as well that such an option could be a good idea, not just for RE but for any bigger changes that strives to be eventually included into the main development line. I'm sure many people on this list would go for experimental just to help testing new features. I personally don't have enough time to help in Vim development, but I'm always happy to run into various issues and report them. "experimental" could be a compilation option as well to avoid having both "old" and "new" code compiled into the program. It should be reported with bug reports like any other compilation option (just as in "happens with big features but not with tiny"). -- -- 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/groups/opt_out.
