-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Development: make lint
always fails using GNU grep 3.8 or later
#3635
Comments
Yes, I agree that it looks like we could shift to checking the exit code to be sure that it's 2. I also think it's worth submitting a PR to vim-vimlint to use |
👍 syngan/vim-vimlint#124 though I'm not too optimistic about it being reviewed/merged any time soon 😅 |
I'm having a hard time duplicating this.
|
Is your version of Equivalently: does $ docker run archlinux:latest egrep --version >/dev/null
egrep: warning: egrep is obsolescent; using grep -E
$ docker run debian:latest egrep --version >/dev/null |
Ah, yup, that would do it. Thank you 🙇 . |
Change scripts/lint to handle the deprecation warning about egrep that's reported on recent non-Debian systems by checking the exit code explicitly instead of merely checking for the presence of output. Fixes fatih#3635
Change scripts/lint to handle the deprecation warning about egrep that's reported on recent non-Debian systems by checking the exit code explicitly instead of merely checking for the presence of output. Fixes fatih#3635
Output of
make lint
This failure is because the
Running vim-vimlint
step is marked as failed when any output is capturedvim-go/scripts/lint
Line 58 in ca6c532
But
vim-vimlint
usesegrep
when run https://github.com/syngan/vim-vimlint/blob/cec40c28f119a5f4b92ceb0b6aae525122a81244/bin/vimlint.sh#L106 since GNUgrep
3.8egrep
is deprecated and emits a warning https://lists.gnu.org/archive/html/info-gnu/2022-09/msg00001.html which is then captured, resulting in failure.Since https://github.com/syngan/vim-vimlint has not been updated in 6 years I don't imagine we can patch there. Maybe the lint script could check the exit code of
vimlin-lint
instead?The text was updated successfully, but these errors were encountered: