vim/syntastic
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
f79e9d2eda
syntastic/syntax_checkers/python/pylint.vim

66 lines
2.1 KiB
VimL
Raw Normal View History

split python checker out into 3 files previously there were 3 checkers in the one file
2012-02-20 05:20:48 -05:00
"============================================================================
"File: pylint.vim
"Description: Syntax checking plugin for syntastic.vim
"Author: Parantapa Bhattacharya <parantapa at gmail dot com>
"
"============================================================================
add guards to all checkers goddamn I love macros
2013-02-21 10:50:41 -05:00
if exists("g:loaded_syntastic_python_pylint_checker")
finish
endif
Cleaner error handling for pylint.
2013-09-20 00:49:19 -04:00
let g:loaded_syntastic_python_pylint_checker = 1
let s:pylint_new = -1
add guards to all checkers goddamn I love macros
2013-02-21 10:50:41 -05:00
refactor how we represent and store checkers using python as a demo Add 2 classes: SyntasticChecker and SyntasticRegistry. SyntasticChecker represents a checker. It holds funcrefs to the checker func, the highlight regex func and a new `isAvailable()` func (that essentially just checks if the checker exe is installed) SyntasticRegistry is responsible for: * loading checkers * storing checkers * fetching the checkers to use according to availability and the users settings Motivation/benefits: * in the current system only one checker can be loaded per filetype * syntax checkers cant be "chained" together * the system is hard to add features to since fundamental concepts like syntax checkers and location lists arent represented explicitly Things left to do: * add a call to g:SyntasticRegistry.CreateAndRegisterChecker() to all checkers * add an `isAvailable` function to all checkers * move all checkers into `syntax_checkers/filetype/checkername.vim` - g:SyntasticRegistry assumes this layout, and its a good idea anyway for consistency and it makes it easier for users to add their own checkers Things to do after all of the above: * add a LocationList class and move all the filtering functions onto it * possibly add an Error class that wraps up each item in a loc list Random notes: * with the new system you can select the checkers to use with e.g. `let g:syntastic_python_checkers=['flake8', 'pylint']` This will try flake8 first, and if no errors are detected it will move onto pylint.
2013-01-23 19:01:30 -05:00
function! SyntaxCheckers_python_pylint_IsAvailable()
Cleaner error handling for pylint.
2013-09-20 00:49:19 -04:00
let s:pylint_new = executable('pylint') ? s:PylintNew() : -1
return s:pylint_new >= 0
refactor how we represent and store checkers using python as a demo Add 2 classes: SyntasticChecker and SyntasticRegistry. SyntasticChecker represents a checker. It holds funcrefs to the checker func, the highlight regex func and a new `isAvailable()` func (that essentially just checks if the checker exe is installed) SyntasticRegistry is responsible for: * loading checkers * storing checkers * fetching the checkers to use according to availability and the users settings Motivation/benefits: * in the current system only one checker can be loaded per filetype * syntax checkers cant be "chained" together * the system is hard to add features to since fundamental concepts like syntax checkers and location lists arent represented explicitly Things left to do: * add a call to g:SyntasticRegistry.CreateAndRegisterChecker() to all checkers * add an `isAvailable` function to all checkers * move all checkers into `syntax_checkers/filetype/checkername.vim` - g:SyntasticRegistry assumes this layout, and its a good idea anyway for consistency and it makes it easier for users to add their own checkers Things to do after all of the above: * add a LocationList class and move all the filtering functions onto it * possibly add an Error class that wraps up each item in a loc list Random notes: * with the new system you can select the checkers to use with e.g. `let g:syntastic_python_checkers=['flake8', 'pylint']` This will try flake8 first, and if no errors are detected it will move onto pylint.
2013-01-23 19:01:30 -05:00
endfunction
function! SyntaxCheckers_python_pylint_GetLocList()
update checkers to use the new syntastic#makeprg#build() Make all the easy updates. There are still quite a few to do, but in doing these ones I can see that syntastic#makeprg#build() needs to accept a few more options. Namely: * "postargs" that appear after the filename * "tail" that appears after everything - used for things like redirecting output and piping to grep/sed/etc * the filename itself - only the java checkers needed this since they specify the directory of the file to check as well There are still a few other things to do as well: * remove the options from the checkers that are now provided by syntastic#makeprg#build implicitly - i.e. the checker exe and args. * also, we need to doc the above implicit checker options
2013-01-20 06:07:05 -05:00
let makeprg = syntastic#makeprg#build({
Postprocessing functions. This patch adds an option 'postprocess' to SyntasticMake(). The value of this option is a list of names. Each name is translated to a function syntastic#postprocess#name(). These functions are applied in order to the list of errors just before SyntasticMake() returns. They take a single parameter, the list of errors, and are supposed to returned the processed list.
2013-05-10 07:11:07 -04:00
\ 'exe': 'pylint',
Cleaner error handling for pylint.
2013-09-20 00:49:19 -04:00
\ 'args': (s:pylint_new ? '--msg-template="{path}:{line}: [{msg_id}] {msg}" -r n' : '-f parseable -r n -i y'),
Make syntastic#makeprg#build() aware of filetypes. Fixes #667.
2013-05-31 14:05:45 -04:00
\ 'filetype': 'python',
Postprocessing functions. This patch adds an option 'postprocess' to SyntasticMake(). The value of this option is a list of names. Each name is translated to a function syntastic#postprocess#name(). These functions are applied in order to the list of errors just before SyntasticMake() returns. They take a single parameter, the list of errors, and are supposed to returned the processed list.
2013-05-10 07:11:07 -04:00
\ 'subchecker': 'pylint' })
Make syntastic#makeprg#build() aware of filetypes. Fixes #667.
2013-05-31 14:05:45 -04:00
Error format fix for pylint.
2013-04-10 04:48:17 -04:00
let errorformat =
Catch up with the latest pylint contortions.
2013-08-07 05:01:45 -04:00
\ '%A%f:%l: %m,' .
\ '%A%f:(%l): %m,' .
Postprocessing functions. This patch adds an option 'postprocess' to SyntasticMake(). The value of this option is a list of names. Each name is translated to a function syntastic#postprocess#name(). These functions are applied in order to the list of errors just before SyntasticMake() returns. They take a single parameter, the list of errors, and are supposed to returned the processed list.
2013-05-10 07:11:07 -04:00
\ '%-Z%p^%.%#,' .
\ '%-G%.%#'
update checkers to use the new syntastic#makeprg#build() Make all the easy updates. There are still quite a few to do, but in doing these ones I can see that syntastic#makeprg#build() needs to accept a few more options. Namely: * "postargs" that appear after the filename * "tail" that appears after everything - used for things like redirecting output and piping to grep/sed/etc * the filename itself - only the java checkers needed this since they specify the directory of the file to check as well There are still a few other things to do as well: * remove the options from the checkers that are now provided by syntastic#makeprg#build implicitly - i.e. the checker exe and args. * also, we need to doc the above implicit checker options
2013-01-20 06:07:05 -05:00
Postprocessing functions. This patch adds an option 'postprocess' to SyntasticMake(). The value of this option is a list of names. Each name is translated to a function syntastic#postprocess#name(). These functions are applied in order to the list of errors just before SyntasticMake() returns. They take a single parameter, the list of errors, and are supposed to returned the processed list.
2013-05-10 07:11:07 -04:00
let loclist=SyntasticMake({
\ 'makeprg': makeprg,
\ 'errorformat': errorformat,
\ 'postprocess': ['sort'] })
Munge the output of pylint in Vim rather than relying on sed(1).
2013-02-06 08:29:56 -05:00
Cleanup. Adds an option g:syntastic_xhtml_tidy_ignore_errors to xhtml/tidy. Cosmetic code changes.
2013-04-15 04:21:52 -04:00
for n in range(len(loclist))
Pylint: ignore informational messages.
2013-08-12 04:22:12 -04:00
let type = loclist[n]['text'][1]
if type =~# '\m^[EF]'
let loclist[n]['type'] = 'E'
elseif type =~# '\m^[CRW]'
let loclist[n]['type'] = 'W'
else
let loclist[n]['valid'] = 0
endif
Catch up with the latest pylint contortions.
2013-08-07 05:01:45 -04:00
let loclist[n]['vcol'] = 0
Cleanup. Adds an option g:syntastic_xhtml_tidy_ignore_errors to xhtml/tidy. Cosmetic code changes.
2013-04-15 04:21:52 -04:00
endfor
update makeprg builder and update some checkers to use it update makeprg builder: * it now accepts `fname`, `tail`, and `post_args` params. * add some doc above syntastic#makeprg#build * update a bunch of checkers to use the new params Still have quite a few checkers that arent using makeprg#build. Including all c* and a few other c-like checkers. And PHP. Not to worried about c* as these checkers are complicated and probably justify having their own logic to build makeprgs.
2013-01-20 07:27:19 -05:00
Postprocessing functions. This patch adds an option 'postprocess' to SyntasticMake(). The value of this option is a list of names. Each name is translated to a function syntastic#postprocess#name(). These functions are applied in order to the list of errors just before SyntasticMake() returns. They take a single parameter, the list of errors, and are supposed to returned the processed list.
2013-05-10 07:11:07 -04:00
return loclist
update makeprg builder and update some checkers to use it update makeprg builder: * it now accepts `fname`, `tail`, and `post_args` params. * add some doc above syntastic#makeprg#build * update a bunch of checkers to use the new params Still have quite a few checkers that arent using makeprg#build. Including all c* and a few other c-like checkers. And PHP. Not to worried about c* as these checkers are complicated and probably justify having their own logic to build makeprgs.
2013-01-20 07:27:19 -05:00
endfunction
refactor how we represent and store checkers using python as a demo Add 2 classes: SyntasticChecker and SyntasticRegistry. SyntasticChecker represents a checker. It holds funcrefs to the checker func, the highlight regex func and a new `isAvailable()` func (that essentially just checks if the checker exe is installed) SyntasticRegistry is responsible for: * loading checkers * storing checkers * fetching the checkers to use according to availability and the users settings Motivation/benefits: * in the current system only one checker can be loaded per filetype * syntax checkers cant be "chained" together * the system is hard to add features to since fundamental concepts like syntax checkers and location lists arent represented explicitly Things left to do: * add a call to g:SyntasticRegistry.CreateAndRegisterChecker() to all checkers * add an `isAvailable` function to all checkers * move all checkers into `syntax_checkers/filetype/checkername.vim` - g:SyntasticRegistry assumes this layout, and its a good idea anyway for consistency and it makes it easier for users to add their own checkers Things to do after all of the above: * add a LocationList class and move all the filtering functions onto it * possibly add an Error class that wraps up each item in a loc list Random notes: * with the new system you can select the checkers to use with e.g. `let g:syntastic_python_checkers=['flake8', 'pylint']` This will try flake8 first, and if no errors are detected it will move onto pylint.
2013-01-23 19:01:30 -05:00
Catch up with the latest pylint contortions.
2013-08-07 05:01:45 -04:00
function s:PylintNew()
Add safety guard for pylint.
2013-09-19 18:16:36 -04:00
try
Safer version check for pylint.
2013-09-23 16:14:46 -04:00
let pylint_version = filter(split(system('pylint --version'), '\m, \=\|\n'), 'v:val =~# "^pylint "')[0]
Cleanup parsing versions.
2013-09-24 01:39:07 -04:00
let ret = syntastic#util#versionIsAtLeast(syntastic#util#parseVersion(pylint_version), [1])
Minor cleanup.
2013-09-24 14:43:12 -04:00
catch /^Vim\%((\a\+)\)\=:E684/
Cleaner error handling for pylint.
2013-09-20 00:49:19 -04:00
call syntastic#util#error("checker python/pylint: can't parse version string (abnormal termination?)")
let ret = -1
Add safety guard for pylint.
2013-09-19 18:16:36 -04:00
endtry
Cleaner error handling for pylint.
2013-09-20 00:49:19 -04:00
return ret
Catch up with the latest pylint contortions.
2013-08-07 05:01:45 -04:00
endfunction
refactor how we represent and store checkers using python as a demo Add 2 classes: SyntasticChecker and SyntasticRegistry. SyntasticChecker represents a checker. It holds funcrefs to the checker func, the highlight regex func and a new `isAvailable()` func (that essentially just checks if the checker exe is installed) SyntasticRegistry is responsible for: * loading checkers * storing checkers * fetching the checkers to use according to availability and the users settings Motivation/benefits: * in the current system only one checker can be loaded per filetype * syntax checkers cant be "chained" together * the system is hard to add features to since fundamental concepts like syntax checkers and location lists arent represented explicitly Things left to do: * add a call to g:SyntasticRegistry.CreateAndRegisterChecker() to all checkers * add an `isAvailable` function to all checkers * move all checkers into `syntax_checkers/filetype/checkername.vim` - g:SyntasticRegistry assumes this layout, and its a good idea anyway for consistency and it makes it easier for users to add their own checkers Things to do after all of the above: * add a LocationList class and move all the filtering functions onto it * possibly add an Error class that wraps up each item in a loc list Random notes: * with the new system you can select the checkers to use with e.g. `let g:syntastic_python_checkers=['flake8', 'pylint']` This will try flake8 first, and if no errors are detected it will move onto pylint.
2013-01-23 19:01:30 -05:00
call g:SyntasticRegistry.CreateAndRegisterChecker({
\ 'filetype': 'python',
refactor all the syntax checkers to use the new API and dir layout
2013-01-27 15:08:30 -05:00
\ 'name': 'pylint' })
Reference in New Issue Copy Permalink