Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Broken vim integration #29

Open
jpfairbanks opened this issue Feb 26, 2016 · 2 comments
Open

Broken vim integration #29

jpfairbanks opened this issue Feb 26, 2016 · 2 comments

Comments

@jpfairbanks
Copy link

:TextLint runs the command and populates the quickfix list but :cnext does not move to the next lint error. I think it is because the errorformat does not match the format of the errors emitted.

Does anyone know how to change the error format in order to make this integration work?
Or if I am totally wrong about the diagnosis, that would be helpful information too.

@cdlm
Copy link
Collaborator

cdlm commented Feb 26, 2016

Apparently I had started work around that: cdlm@78785e8
I don't recall what state it's in, but you might want to have a look…

@jpfairbanks
Copy link
Author

I took out the character information using sed and now vim can parse the error messages and get me to the right line.

In textline.bash

if [[ ! -e textlint.log ]]; then
    echo Something bad happened!
    exit 1
else
    # attempting to make this work with vim plugin loses the character details of the error
    sed 's/\([^:]*\):\([0-9]*\).[^:]*:\(.*\)$/\1:\2:\3/' < textlint.log
    exit 0
fi

That is more helpful to me than it not working but I would like to be able to keep the character info.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants