[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#57884: [PATCH] Flymake backend using the shellcheck program
From: |
Stefan Kangas |
Subject: |
bug#57884: [PATCH] Flymake backend using the shellcheck program |
Date: |
Sat, 17 Sep 2022 14:17:54 -0400 |
Eli Zaretskii <eliz@gnu.org> writes:
> If we don't expect users to customize this, maybe this shouldn't be a
> defcustom at all? If and when we learn about an alternative program,
> we could at that time decide how best to allow its customization.
Makes sense.
> For example, if both programs don't need any command-line switches, we
> could offer a defcustom only for the program.
Maybe we should just make the flags into a defcustom, because there are
some useful ones like, from shellcheck(1):
-i CODE1[,CODE2...], --include=CODE1[,CODE2...]
Explicitly include only the specified codes in the report
-e CODE1[,CODE2...], --exclude=CODE1[,CODE2...]
Explicitly exclude the specified codes from the report.
--norc Don't try to look for .shellcheckrc configuration files.
-s shell, --shell=shell
Specify Bourne shell dialect. Valid values are sh, bash, dash
and ksh.
- bug#57884: [PATCH] Flymake backend using the shellcheck program, Augusto Stoffel, 2022/09/17
- bug#57884: [PATCH] Flymake backend using the shellcheck program, Eli Zaretskii, 2022/09/17
- bug#57884: [PATCH] Flymake backend using the shellcheck program, Philip Kaludercic, 2022/09/18
- bug#57884: [PATCH] Flymake backend using the shellcheck program, Augusto Stoffel, 2022/09/18
- bug#57884: [PATCH] Flymake backend using the shellcheck program, Philip Kaludercic, 2022/09/18
- bug#57884: [PATCH] Flymake backend using the shellcheck program, Augusto Stoffel, 2022/09/18
- bug#57884: [PATCH] Flymake backend using the shellcheck program, Philip Kaludercic, 2022/09/18
- bug#57884: [PATCH] Flymake backend using the shellcheck program, Augusto Stoffel, 2022/09/18
- bug#57884: [PATCH] Flymake backend using the shellcheck program, Philip Kaludercic, 2022/09/18