syntastic

Syntastic close error window and original file window

十年热恋 提交于 2019-12-05 06:05:54
I've installed Syntastic from GitHub and I'm trying to use Syntastic for checking perl syntax errors (and planning to use for Python in a short while). When I use ':quit' or ':q', only original file window closes. The error window does not close. Below is snip from my .vimrc file : execute pathogen#infect() set statusline+=%#warningmsg# set statusline+=%{SyntasticStatuslineFlag()} set statusline+=%* let g:syntastic_perl_checkers = ['perl'] let g:syntastic_python_checkers = ['pylint'] let g:syntastic_enable_perl_checker = 1 let g:syntastic_always_populate_loc_list = 1 let g:syntastic_auto_loc

Can't get “Syntastic” vim plugin to work

喜你入骨 提交于 2019-12-04 17:04:26
问题 I've installed Syntastic plugin in vim. I can't get it to work. I've tried :SyntasticEnable but no luck. SyntasticEnable python in my vimrc doesn't work either (in fact, it doesn't even parse the command, an error is shown when I try to add it to my .vimrc : Not an editor command: SyntasticEnable python ). How can I know what's going on? Syntastic isn't showing errors when I call it from vim. Does the first error ( not and editor command in my .vimrc ) indicates something I'm unaware of? I

How can I configure the omnisharp syntastic syntax checker to be more lenient?

二次信任 提交于 2019-12-04 06:55:46
I've followed this guide for setting up my vim for c#. I works beautifully, but I've got an annoyance: The syntastic checker is a bit too harsh on me. Specifically it advises me to change this line: var parser = new Parser(configuration, findReservations: true); with the message "Redundant argument name specification". Of course I COULD just do as it says, but I happen to like my redundant argument specification. The reader of my code might not remember what that boolean is for otherwise. So... how can I tell syntastic (or omnisharp) to relax about this kind of warning? jasoni Modify the

How can I set the Python max allowed line length to 120 in Syntastic for Vim?

我是研究僧i 提交于 2019-12-03 22:49:40
I'm using python-mode for Vim, I prefer for there to be 120 character lines rather than the stark 80 as defined in the PEP8 standard. In python-mode, this is easy. I just add the following to my ~/.vimrc: " Pylint configuration file let g:pymode_lint_config = '$HOME/.pylint.rc' let g:pymode_options_max_line_length=120 This works great, but then, I also wanted to use the superb Syntastic plugin for checking syntax of various other kinds (Chef recipes for foodcritic, for example.) Unfortunately, Syntastic also does Python linting, and as such it has now started complaining about my 120 character

Disable pep8 check in syntastic for python files

别等时光非礼了梦想. 提交于 2019-12-03 11:52:58
问题 I work with enough code that does not follow pep8 (that I cannot fix) and would like syntastic to not use the pep8 syntax checker. Any way to disable it? 回答1: If your are using flake8 as a python syntax checker you could do it like this (put it into your vimrc or ftplugin/python.vim file): let g:syntastic_python_checkers=['flake8'] let g:syntastic_python_flake8_args='--ignore=E501,E225' You need to silence each error class explicitly (and cannot disable pep8 checking as a whole). See the

How to avoid “‘main’ is not defined in module ‘Main’” when using syntastic

无人久伴 提交于 2019-12-03 11:45:15
问题 I'm trying to write a module in Haskell. It does not have a main because it's not meant to be a stand-alone program. I just started using syntastic, and it is constantly reporting: The IO action ‘main’ is not defined in module ‘Main’ This is preventing it from reporting other real errors in my module. If I try to work around this by adding a dummy main, it starts complaining that everything else is "Defined but not used". How can I tell syntastic (and whatever checker it's using under the

How to configure Syntastic with JSHint?

自古美人都是妖i 提交于 2019-12-03 04:54:14
问题 How to use the Syntastic Vim plugin with JSHint to validate JavaScript code? Environment: Ubuntu 11.04 VIM - Vi IMproved 7.3 What I have installed, following the solution at VIM + JSLint?: Vundle node.js Node Package Manager jshint, globally Syntastic installed through Vundle (Used the :BundleInstall command inside Vim to make sure Syntastic was installed.) .vimrc: set nocompatible " be iMproved filetype off " required! set rtp+=~/.vim/bundle/vundle/ call vundle#rc() " let Vundle manage

Disable pep8 check in syntastic for python files

守給你的承諾、 提交于 2019-12-03 02:14:13
I work with enough code that does not follow pep8 (that I cannot fix) and would like syntastic to not use the pep8 syntax checker. Any way to disable it? If your are using flake8 as a python syntax checker you could do it like this (put it into your vimrc or ftplugin/python.vim file): let g:syntastic_python_checkers=['flake8'] let g:syntastic_python_flake8_args='--ignore=E501,E225' You need to silence each error class explicitly (and cannot disable pep8 checking as a whole). See the flake8 documentation and pycodestyle documentation (used to be pep8) for all error and warning codes. Adding to

How to avoid “‘main’ is not defined in module ‘Main’” when using syntastic

懵懂的女人 提交于 2019-12-03 01:18:15
I'm trying to write a module in Haskell. It does not have a main because it's not meant to be a stand-alone program. I just started using syntastic, and it is constantly reporting: The IO action ‘main’ is not defined in module ‘Main’ This is preventing it from reporting other real errors in my module. If I try to work around this by adding a dummy main, it starts complaining that everything else is "Defined but not used". How can I tell syntastic (and whatever checker it's using under the covers) that there isn't supposed to be a main ? Testing with ghc-mod (which backs syntastic, although

Syntastic for Vim: What are the required lines in ~/.vimrc? (PHP error checking)

点点圈 提交于 2019-11-30 19:45:32
I find the documents frustrating. What are the basic lines I need to add to my config file to get it working? Technically, nothing. If you've extracted Syntastic into your .vim directory, try using the :SyntasticEnable command within Vim to enable it for the filetype of the currently open file. If you want to automatically turn it on for a given filetype, then you'll want to put a... SyntasticEnable [filetype] line in your .vimrc where [filetype] is the type of file you want to enable it for. 来源: https://stackoverflow.com/questions/2368208/syntastic-for-vim-what-are-the-required-lines-in-vimrc