ale - Check syntax in Vim asynchronously and fix files, with Language Server Protocol (LSP) support

Age	Commit message (Collapse)	Author
2019-07-02	Support csc, update mcsc (#2586)	hernot
	* Added a new csc linter for C# code. * More output is now handled for mcsc.
2018-10-29	Add a note about OmniSharp	w0rp

2018-09-04	add uncrustify fixer for several languages	Derek P Sifford

2018-03-22	Fit documentation to the column size in ale-cs.txt	w0rp

2018-03-22	Added the word 'find' as it was missing in docs/ale-cs.txt	Ashley Smith

2018-02-23	Add Unity project path to Unity example in docs	David Briscoe
	For Ale to recognize the symbols in your project, you need to point it at where Unity builds your assemblies. Add this path to the example.
2017-12-25	Fix c# documentation variable typo	Yaroslav Ryabukha

2017-12-19	Fix mcsc paths and escaping for Windows	w0rp

2017-12-19	Fix #1226 - Update the mcsc documentation to make it clearer how to use it	w0rp

2017-09-27	Implemented review recommendations	Xristoph Hintermüller
	Implements suggestions and recommendations suggested by the first review of the "Advance C# linter based on mcs -t:module (#952)" pull request. - Clarifies and simplifies description of linters and options - Added links to help file and marked the mcsc linter as to be run only when file in buffer is saved or loaded. - Added comments to the mcsc.vim file to clarify code - removed type checks considered not necessary be reviewer. - addresses findings by vader - removed call to getcwd and cd in vim script - handler expands file names relative to route of source tree into absolute pathes. Fixes errors not being marked when vim is started from subdirectory of source tree. - implements tests for mcs.vim and mcsc.vim linter
2017-09-25	Added advanced c-sharp linter	Xristoph Hintermüller
	The existing c-charp linter used the --syntax check mode of the mono mcs compiler only. The new mcsc linter tries to compile the files located in a directory tree located bejond the specified source directory or the current one if no source is explicitly specified. The resulting module target is placed in a temporary file managed by ale.