Skip to content
This repository has been archived by the owner on Sep 20, 2023. It is now read-only.

Puppet: caught error output w/o line and column #2239

Open
wants to merge 1,448 commits into
base: master
Choose a base branch
from

Conversation

Slm0n87
Copy link

@Slm0n87 Slm0n87 commented Jan 6, 2019

solves #1948

lcd047 and others added 30 commits June 5, 2016 11:18
- Mark variable g:syntastic_cuda_arch as deprecated.
- Create temporary files in the base directory of the file being
  checked, rather than the current directory.
- Remove temporary files after use.
Removes unexpected argument causing error from mlint.
…tlab-mlint-update

Checker mlint: fix arguments.
README: update instructions to reduce download size.
Checker "tsc" has been removed, in favour of the external checker
"tsuquyomi" (https://github.com/Quramy/tsuquyomi).

Reference: vim-syntastic#1811
elvis and others added 17 commits June 15, 2018 15:11
Signed-off-by: Zang MingJie <zealot0630@gmail.com>
Bug fix: don't get triggered for preview window.
When the "--strict" or "--subjective" options are added to checkpatch's
arguments, it will return additional warnings of this format type:

> file.c:123: CHECK: Alignment should match open parenthesis

The extra warnings can be enabled with:

> let g:syntastic_c_checkpatch_args = "--strict"

Signed-off-by: Brandon Maier <brandon.maier@rockwellcollins.com>
…ict-errors

Checker c/checkpatch: handle strict warnings.
ansible-lint now has a slightly different outputformat for errors:

prepare-host.yaml:24: [E302] chmod used in place of argument mode to
file module

Append the errorformat so this gets recognized by syntastic.
…format

Checker ansible/ansible_lint: fix errorformat
@lcd047
Copy link
Collaborator

lcd047 commented Jan 6, 2019

Sadly, this breaks error sorting (cf. :h syntastic-config-sort).

@Slm0n87
Copy link
Author

Slm0n87 commented Jan 6, 2019

thx for the quick feedback. you are right.
in my case the output of the puppet-parser is shown at first - before the output of puppet-lint. which is absolut OK for me from usibility perspective, but I understand that you prefer to assign the error to a line :(

lcd047 and others added 9 commits January 22, 2019 15:06
Path: syntastic/syntax_checkers/c/oclint.vim
Line: 28
Char: 106
Correction: ' ' -> ')'
Apply the same changes that were applied to html/validator in
vim-syntastic#2241 to w3/html so that it can be used to
validate SVG and XHTML as well.

Add support for `g:syntastic_{type}_w3_doctype` to control the doctype
POST parameter sent to the validator.  This is necessary for SVG without
a DTD (which would otherwise be validated as generic XML) and useful for
all the types to control validation.

Signed-off-by: Kevin Locke <kevin@kevinlocke.name>
Apply the same changes that were applied to html/validator in
vim-syntastic#2241 to w3/html so that it can be used to
validate SVG and XHTML as well.

Add support for `g:syntastic_{type}_w3_doctype` to control the doctype
POST parameter sent to the validator.  This is necessary for SVG without
a DTD (which would otherwise be validated as generic XML) and useful for
all the types to control validation.

Signed-off-by: Kevin Locke <kevin@kevinlocke.name>
- like 'Syntax error at end of input'
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet