vim/syntastic
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

README: minor cleanup.

Browse Source
This commit is contained in:
LCD 47 2014-12-04 11:05:12 +02:00
parent 6b9a348423
commit 38ba360733
1 changed files with 16 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
README.markdown
View File

@ -36,7 +36,8 @@
3.10. [I have enabled multiple checkers for the current filetype. How can I display all of the errors from all of the checkers together?](#faqaggregate) 3.10. [I have enabled multiple checkers for the current filetype. How can I display all of the errors from all of the checkers together?](#faqaggregate)
3.11. [How can I jump between the different errors without using the location list at the bottom of the window?](#faqlnext) 3.11. [How can I jump between the different errors without using the location list at the bottom of the window?](#faqlnext)
3.12. [The error window is closed automatically when I :quit the current buffer but not when I :bdelete it?](#faqbdelete) 3.12. [The error window is closed automatically when I :quit the current buffer but not when I :bdelete it?](#faqbdelete)
4. [Other resources](#otherresources) 4. [Resources](#otherresources)
- - - - - -
<a name="introduction"></a> <a name="introduction"></a>
@ -154,7 +155,7 @@ following:
<a name="faqinfo"></a> <a name="faqinfo"></a>
__Q. I installed syntastic but it isn't reporting any errors...__ __3.1.\ Q. I installed syntastic but it isn't reporting any errors...__
A. The most likely reason is that none of the syntax checkers that it requires A. The most likely reason is that none of the syntax checkers that it requires
is installed. For example: by default, python requires either `flake8` or is installed. For example: by default, python requires either `flake8` or
@ -170,7 +171,7 @@ create an issue - or better yet, create a pull request.
<a name="faqpython3"></a> <a name="faqpython3"></a>
__Q. The `python` checker complains about syntactically valid Python 3 constructs...__ __3.2.\ Q. The `python` checker complains about syntactically valid Python 3 constructs...__
A. Configure the `python` checker to call a Python 3 interpreter rather than A. Configure the `python` checker to call a Python 3 interpreter rather than
Python 2, e.g: Python 2, e.g:
@ -180,7 +181,7 @@ let g:syntastic_python_python_exec = '/path/to/python3'
<a name="faqhtml5"></a> <a name="faqhtml5"></a>
__Q. Are there any local checkers for HTML5 that I can use with syntastic?__ __3.3.\ Q. Are there any local checkers for HTML5 that I can use with syntastic?__
[HTML Tidy][18] has a fork named [HTML Tidy for HTML5][19]. It's a drop [HTML Tidy][18] has a fork named [HTML Tidy for HTML5][19]. It's a drop
in replacement, and syntastic can use it without changes. Just install it in replacement, and syntastic can use it without changes. Just install it
@ -198,7 +199,7 @@ let g:syntastic_html_validator_api = 'http://localhost:8888/'
<a name="faqperl"></a> <a name="faqperl"></a>
__Q. The `perl` checker has stopped working...__ __3.4.\ Q. The `perl` checker has stopped working...__
A. The `perl` checker runs `perl -c` against your file, which in turn A. The `perl` checker runs `perl -c` against your file, which in turn
__executes__ any `BEGIN`, `UNITCHECK`, and `CHECK` blocks, and any `use` __executes__ any `BEGIN`, `UNITCHECK`, and `CHECK` blocks, and any `use`
@ -214,7 +215,7 @@ let g:syntastic_enable_perl_checker = 1
<a name="faqrust"></a> <a name="faqrust"></a>
__Q. What happened to the `rustc` checker?__ __3.5.\ Q. What happened to the `rustc` checker?__
A. It has been included in the [Rust compiler package][12]. If you have A. It has been included in the [Rust compiler package][12]. If you have
a recent version of the Rust compiler, the checker should be picked up a recent version of the Rust compiler, the checker should be picked up
@ -222,8 +223,8 @@ automatically by syntastic.
<a name="faqloclist"></a> <a name="faqloclist"></a>
__Q. I run a checker and the location list is not updated...__ __3.6.\ Q. I run a checker and the location list is not updated...__
__Q. I run`:lopen` or `:lwindow` and the error window is empty...__ __3.6.\ Q. I run`:lopen` or `:lwindow` and the error window is empty...__
A. By default the location list is changed only when you run the `:Errors` A. By default the location list is changed only when you run the `:Errors`
command, in order to minimise conflicts with other plugins. If you want the command, in order to minimise conflicts with other plugins. If you want the
@ -235,7 +236,7 @@ let g:syntastic_always_populate_loc_list = 1
<a name="faqargs"></a> <a name="faqargs"></a>
__Q. How can I pass additional arguments to a checker?__ __3.7.\ Q. How can I pass additional arguments to a checker?__
A. Almost all syntax checkers use the `makeprgBuild()` function. Those checkers A. Almost all syntax checkers use the `makeprgBuild()` function. Those checkers
that do can be configured using global variables. The general form of the that do can be configured using global variables. The general form of the
@ -251,7 +252,7 @@ See `:help syntastic-checker-options` for more information.
<a name="faqcheckers"></a> <a name="faqcheckers"></a>
__Q. Syntastic supports several checkers for my filetype - how do I tell it __3.8.\ Q. Syntastic supports several checkers for my filetype - how do I tell it
which one(s) to use?__ which one(s) to use?__
A. Stick a line like this in your vimrc: A. Stick a line like this in your vimrc:
@ -292,7 +293,7 @@ filetype of the current file is `php`).
<a name="faqstyle"></a> <a name="faqstyle"></a>
__Q. What is the difference between syntax checkers and style checkers?__ __3.9.\ Q. What is the difference between syntax checkers and style checkers?__
A. The errors and warnings they produce are highlighted differently and can A. The errors and warnings they produce are highlighted differently and can
be filtered by different rules, but otherwise the distinction is pretty much be filtered by different rules, but otherwise the distinction is pretty much
@ -322,7 +323,7 @@ See `:help syntastic_quiet_messages` for details.
<a name="faqaggregate"></a> <a name="faqaggregate"></a>
__Q. I have enabled multiple checkers for the current filetype. How can I __3.10.\ Q. I have enabled multiple checkers for the current filetype. How can I
display all of the errors from all of the checkers together?__ display all of the errors from all of the checkers together?__
A. Set `g:syntastic_aggregate_errors` to 1 in your vimrc: A. Set `g:syntastic_aggregate_errors` to 1 in your vimrc:
@ -334,7 +335,7 @@ See `:help syntastic-aggregating-errors` for more details.
<a name="faqlnext"></a> <a name="faqlnext"></a>
__Q. How can I jump between the different errors without using the location __3.11.\ Q. How can I jump between the different errors without using the location
list at the bottom of the window?__ list at the bottom of the window?__
A. Vim provides several built-in commands for this. See `:help :lnext` and A. Vim provides several built-in commands for this. See `:help :lnext` and
@ -346,7 +347,7 @@ mappings (among other things).
<a name="faqbdelete"></a> <a name="faqbdelete"></a>
__Q. The error window is closed automatically when I :quit the current buffer __3.12.\ Q. The error window is closed automatically when I :quit the current buffer
but not when I :bdelete it?__ but not when I :bdelete it?__
A. There is no safe way to handle that situation automatically, but you can A. There is no safe way to handle that situation automatically, but you can
@ -359,7 +360,7 @@ cabbrev <silent> bd lclose\|bdelete
<a name="otherresources"></a> <a name="otherresources"></a>
## 4\. Other resources ## 4\. Resources
The preferred place for posting suggestions, reporting bugs, and general The preferred place for posting suggestions, reporting bugs, and general
discussions related to syntastic is the [issue tracker at GitHub][4]. discussions related to syntastic is the [issue tracker at GitHub][4].