I have flake8-docstrings plugin installed and some others. But for some runs I want to ignore all the warnings of this plugin in some easy way: without creating a config file and without making a list of it's warning codes manually.
Is there any solution like:
flake8 . --ignore=Dxxx
or
flake8 . --disable-plugin=docstrings
?
You're almost there
flake8 --extend-ignore=D .
Will ignore all violations reported that start with D and flake8-docstrings is the only plugin that reports codes starting with D.
If you have suggestions on how to improve this section of documentation that describes how to do it, please open an issue.
Related
Yes, I've checked the other similar questions.
I manually installed the schlepp plugin. It's in the bundle directory, next to plugins that are working. In fact, I also put it in the plugin directory.
I put the runtime line in my .vimrc, and verified in vim that it's working. I even did vim -V, and saw that vim is looking in the schlepp folder. And yet, if I do ":help schlepp", it says, "Sorry, no help for schlepp."
If you read the documentation for the plugin, you'll find the instructions for manual installation, which hint quite distinctly at using a plugin manager.
Presuming you have indeed copied the plugin correctly, I guess you forgot :helptags doc.
The plugin seems rather unmaintained. Why not have a look at vim-move instead?
I seem to have to run RopeGenerateAutoimportCache every time I open my python project in vim before RopeAutoImport will work. If I run RopeAutoImport before caching the projects modules I get the following error:
Global name my_func not found!
Is there a way of either generating the cache on each vim startup, or preferably, saving the cache to be reread on startup?
I went back to python-mode (which is the suggested plugin for python) and found a problem in the code for which, at the time writing this, I have a patch to be merged: github.com/klen/python-mode/pull/488
I am no longer seeing this problem with the patched code.
I would really like to use easytags, but after following Odding's installation instructions, that is first installing misc and then installing easytags, at startup vim is throwing the "misc is not installed,easytags is broken" error. I am just unzipping them into my vim directory as I have always done with other plugins.. Any suggestions? thanks!
Installation is indeed a simple unzipping of both misc.zip and easytags.zip into the same ~/.vim/ directory.
Check out the :scriptnames command from Vim to see whether all files got successfully sourced. After a manual :runtime autoload/xolox/misc.vim, it should contain entries like:
205: ~/.vim/autoload/xolox/misc.vim
278: ~/.vim/plugin/easytags.vim
If you're still facing problems, please open an issue on the plugin's issue tracker.
I have a problem with installing SuperTab from vimball. I get an error:
E739: Cannot create directory: C:\Users\Pawe<b3>\vimfiles
I guess the problem is the directory name which is C:\Users\Paweł\vimfiles. Is there a way to solve it without changing directory name? Btw: I have set encoding=UTF-8 in my vimrc.
Edit:
The way I install it is so: download .vmb file, open it with vim (using context menu: 'edit with vim') and then I write :so %. And the error occurs.
Using :set verbose=20 I get http://pastebin.com/BLaeLzuU (those are things I found interesting).
And here's the wider story. I was trying to install plugins using vimballs, because I failed running plugins with pathogen (identical case as here: https://github.com/tpope/vim-pathogen/issues/110. In fact my output of :scritpnames is here: http://pastebin.com/YBTBvsvz). To tell you the truth I even tried to copy folder plugin form plugins git repo to my ~\vimfiles. With no success (they are not mentioned in scriptnames). And so I don't have any clue what is going on. Only that output from vimball tells me that it could be the path name. Other then that, I'm hopeless.
Btw: using Windows 8 if that's a deal breaker.
Eventually I have renamed the user name and user folder because the directory name was a problem for other aplications too. Here are the instructions: https://superuser.com/questions/495290/how-to-rename-user-folder-in-windows-8
This question has been asked, in one form or another, a dozen times here, and it blows my mind how not a single one actually addresses how to configure syntastic or jslint such that it actually does what it is supposed to do (its README file is completely useless)
see here
Can anyone provide some step by step instructions, or a link to such instructions. I tried to install jslint and spidermonkey, and I got nowhere.
I managed to get the syntax check to work (thanks to romainl). A few things I learned along the way that may help anyone with a similar problem
To build Javascript Lint look for the README file nested in jsl-x.x.x/src/README.html
The build instructions are gmake -f Makefile.ref but gmake is the same thing as make so issue the command sudo ln -s /usr/bin/make /usr/bin/gmake
jsl will now be found in jsl-0.3.0/src/Linux_All_DBG.OBJ/jsl. To make it generally accessible do something like: ln -s /whatever/jsl-0.3.0/src/Linux_All_DBG.OBJ /home/ForestGump/bin/jsl. More information here
To check that jsl actually works find a test file ( here) then issue the command jsl -process test.js. It should list all the errors.
To customize your command line, add this to your vimrc file set statusline=%{SyntasticStatuslineFlag()}
What did you do? What works and what doesn't? Do you get error messages?
Here is what I did:
Downloaded the jsl sources from the JavaScript Lint site.
Built jsl and moved it somewhere in my $PATH.
Checked if it worked by running it against a random .js file
Downloaded and installed Syntastic as a Pathogen bundle.
Typed :helptags /path/to/syntastic/doc because for some reason Pathogen's automatic help tags generation doesn't work for me.
Read Syntastic's documentation: :help syntastic.
Steps 1 to 5 didn't take more than 3 or 4 minutes, maybe less.
Step 6 is obligatory, whatever new tool you try. RTFM.
I didn't have to configure anything beside these 3 lines in my .vimrc (and I believe the third is redundant):
let g:syntastic_auto_loc_list=1
let g:syntastic_disabled_filetypes=['html']
let g:syntastic_enable_signs=1
and customizing my statusline a bit with:
%{SyntasticStatuslineFlag()}
EDIT
Here is my statusline:
set statusline=%<\ %n:%f\ %m%r%y%{SyntasticStatuslineFlag()}%=line:\ %l\ of\ %L,\ col:\ %c%V,\ win:\ %{WindowNumber()}\
Don't copy it verbatim or you'll get some errors due to the function call at the end. There is a paragraph about that in syntastic's help.
END EDIT
After all that, 10 or 12 minutes if you count reading the documentation, I have a very helpful location list and signs poping up each time I save a .js file with syntax errors.
Setup vundle according to its README.
Put this into your .vimrc:
Bundle 'scrooloose/syntastic'
Then enter this command in vim:
:BundleInstall
That's it.
EDIT: Vundle has changed its syntax since I originally wrote this. Nowadays, you use
Plugin 'scrooloose/syntastic'
and then enter
:PluginInstall