Welcome to the public Flycheck channel. Ask questions and discuss development. Please follow our Code of Conduct.
go home :)
i'm gonna keep going at this, don't merge it YET
It's quite annoying for myself to get these false errors
$ pug -b /home/rob/pug/foo/bar/baz -p /home/rob/pug/foo/bar/baz < /home/rob/pug/foo/bar/baz/pug-extends.pug
it seems to assume the /home/rob/pug/foo/bar
Need to fix this before I continue
not just once
I got it working
:)
So far I'm counting 3
@aaronjensen Predicates run each time a checker is invoked
They are supposed to be cheap and fast… if there's a more expensive check to be done for a checker that's best left to a separate extension that runs this check in a mode hook and disables the syntax checker via
flycheck-disabled-checkers once
we could run
eslint --print-config in the predicate if it's not too slow
but thinking of it… why not introduce a new checker field, i.e.
:enable whose value is a function which Flycheck calls the first time the checker is to be used in the current buffer. If the function returns nil the checker is put into flycheck-disabled-checkers…
we can even discard its output to run faster
rather than the whole thing in the tests
I'm almost done :)
and this time it works :)
I hit all error patterns
(I think)
I'm about 99% certain anyways :)
Hey guys, does setting
flycheck-clang-include-path work in recursive way?