summaryrefslogtreecommitdiff
path: root/ale_linters/cs/mcsc.vim
AgeCommit message (Collapse)Author
2021-03-01Close #2281 - Separate cwd commands from commandsw0rp
Working directories are now set seperately from the commands so they can later be swapped out when running linters over projects is supported, and also better support filename mapping for running linters on other machines in future.
2019-07-02Support csc, update mcsc (#2586)hernot
* Added a new csc linter for C# code. * More output is now handled for mcsc.
2019-02-22#2132 - Replace all uses of foo_callback with foow0rp
2019-01-26#2132 Unify temporary file management in command.vimw0rp
2018-07-15Massively reduce the amount of code needed for linter testsw0rp
2018-07-12Fix #1716 - Replace tempdir() with a wrapper to preserve TMPDIRw0rp
2018-03-02Try to fix it againw0rp
2017-12-19Fix mcsc paths and escaping for Windowsw0rp
2017-11-19#852 - Capture error codes for mcs and mcscw0rp
2017-09-27Implemented review recommendationsXristoph 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-25Added advanced c-sharp linterXristoph 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.