Bjorn Neergaard dc58db7640 Implement a more efficient statusbar ... The statusbar now keeps its state in a separate variable, in order to avoid excess iterations. The engine now updates said variable on run, and a new function is made available for external statusbars to call (to avoid dependencies on internal implementation details of ale). To keep things light, the status bar code is not loaded unless invoked by the user or an external plugin. On the first load it will update itself from the global loclist, after that, the engine will handle all updates. The external integration function, `ale#statusline#Count()`, will return a tuple in the format [E, W] (where E is errors, W is warnings), unless no data exists (ie, the plugin doesn't have a linter for a file or has not run yet), in which case it returns 0/false.		2016-10-13 08:51:38 -05:00
..
ale	Implement a more efficient statusbar	2016-10-13 08:51:38 -05:00
ale.vim	Use explicit scope in the ale core, as advised by vint -s	2016-10-11 06:14:20 -05:00