On Tue, Aug 20, 2013 at 9:29 PM, Ingo Karkat <sw...@ingo-karkat.de> wrote: [...] > I came to the same conclusion: While it is noble that the Vim syntax > plugin notifies the user that the used script interpreter is not > available in the current editor, having huge blocks of red error > highlighting is certainly overdoing it and counterproductive, because, > as we all know, reality isn't either black or white, and situations like > these do happen.
Signed. > The following patch is for Perl and Python (the two languages I'm > concerned with) only, but I'd be trivial to extend to all languages. Appreciated. Applied. Thanks. Testing with Python 2 and 3, Perl absent. > Charles, would you please consider including something like that? (Maybe > conditionally with a config variable, if there are indeed purists that > prefer the status quo, though none have spoken up so far in this thread.) Only performance issues might turn me purist. I can hardly imagine an environment right now, where one of the two approaches fails significantly more than the other. I expect to be proven wrong and keep a copy of the patch nearby. my 2 ct. --peter. -- -- 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 vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
