recentpopularlog in

kme : linter   37

GitHub - btford/write-good: Naive linter for English prose
Naive linter for English prose. Contribute to btford/write-good development by creating an account on GitHub.
english  language  grammar  writing  linter  stylechecker  nodejs  npm 
june 2019 by kme
GitHub - python/black: The uncompromising Python code formatter
The uncompromising Python code formatter. Contribute to python/black development by creating an account on GitHub.
python  formatter  linter  codestyle  opinionated  alternativeto  pycodestyle 
june 2019 by kme
GitHub - PyCQA/flake8-bugbear: A plugin for Flake8 finding likely bugs and design problems in your program. Contains warnings that don't belong in pyflakes and pycodestyle.
A plugin for Flake8 finding likely bugs and design problems in your program. Contains warnings that don't belong in pyflakes and pycodestyle. - PyCQA/flake8-bugbear
python  flake8  codestyle  formatter  linter 
june 2019 by kme
Question: why does PEP8 recommend leaving a blank line at the end of a .py file? : Python | https://www.reddit.com/
I still cannot find where in PEP 8 it says this, though.
The newline character is considered a line terminator, not a line delimiter.

This is right, but I think still somewhat confusing to some people. The point is that every line should end with a newline, because as was pointed out the newline is considered a line terminator.

I think the proper way to think of it is not to think of it as a blank line at the end of the file - that blank line appears in text editors, but if you were to open the file in python or most programming languages and do readlines, you wouldn't see any blank line at the end. The newline would be the last character in the last line which would be the line before the apparent blank line.
pep8  codestyle  linter  newline  textprocessing  explained 
december 2018 by kme
uncrustify/uncrustify: Code beautifier
Source Code Beautifier for C, C++, C#, ObjectiveC, D, Java, Pawn and VALA
devel  cplusplus  linter  codingstyle  alternativeto  artisticstyle 
december 2017 by kme
autopep8 1.3.3 : Python Package Index
<code class="language-bash">
$ autopep8 --in-place --aggressive --aggressive --max-line-length 78 <filename>
</code>
pep8  linter  devel  codingstyle  solution 
december 2017 by kme
vim-syntastic/syntastic: Syntax checking hacks for vim
set statusline+=%#warningmsg#
set statusline+=%{SyntasticStatuslineFlag()}
set statusline+=%*

let g:syntastic_always_populate_loc_list = 1
let g:syntastic_auto_loc_list = 1
let g:syntastic_check_on_open = 1
let g:syntastic_check_on_wq = 0


Why don't any of the checkers work for Perl? I dunno. This advice doesn't do anything:
4.13. Q. The perl checker has stopped working...

A. The perl checker runs perl -c against your file, which in turn executes any BEGIN, UNITCHECK, and CHECK blocks, and any use statements in your file (cf. perlrun). This is probably fine if you wrote the file yourself, but it's a security problem if you're checking third-party files. Since there is currently no way to disable this behaviour while still producing useful results, the checker is now disabled by default. To (re-)enable it, make sure the g:syntastic_perl_checkers list includes perl, and set g:syntastic_enable_perl_checker to 1 in your vimrc:

let g:syntastic_enable_perl_checker = 1
vim  plugin  linter  syntaxchecking  essential  movein  staticanalysis 
january 2017 by kme
Documentation
Disable Warnings with Control Comment

JavaScript Lint has limited support for control comments. To disable warnings in part of your JavaScript file, you can add the following comments:

/*jsl:ignore*/
(code that fires warnings)
/*jsl:end*/
javascript  jsl  linter  warnings  devel  solution 
august 2015 by kme
vim - How to configure Syntastic with JSHint? - Stack Overflow - http://stackoverflow.com/
For some reason, 'jsl' isn't automatically detected or enabled on CentOS 6.
Here is a more updated info, there is a configuration to associate a file extension to a checker,
in your .vimrc

let g:syntastic_javascript_checkers = ['jshint']

Also to get info about what's going on run this command in vim

:SyntasticInfo

And you'll get an output similar to this:

Syntastic info for filetype: javascript

Available checkers: gjslint jshint

Currently active checker(s): gjslint

Press ENTER or type command to continue
javascript  vim  linter  devel  solution 
july 2015 by kme
Artistic Style - Index
These options work well:

astyle -A2 -xC80 -xL -Y -p
cplusplus  java  c  linter  codestyle  formatter  utility  software 
april 2015 by kme

Copy this bookmark:





to read