From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, Augusto Stoffel <arstoffel@gmail.com>
Cc: 57884@debbugs.gnu.org
Subject: bug#57884: [PATCH] Flymake backend using the shellcheck program
Date: Sat, 17 Sep 2022 14:17:54 -0400 [thread overview]
Message-ID: <CADwFkm=3v5TMyuMKnq-NDgWkOZRwJgKdcXjDn2t=LTfQc_sOMw@mail.gmail.com> (raw)
In-Reply-To: <837d2128io.fsf@gnu.org>
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.
next prev parent reply other threads:[~2022-09-17 18:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 16:48 bug#57884: [PATCH] Flymake backend using the shellcheck program Augusto Stoffel
2022-09-17 17:05 ` Eli Zaretskii
2022-09-17 17:32 ` Augusto Stoffel
2022-09-17 17:52 ` Eli Zaretskii
2022-09-17 18:17 ` Stefan Kangas [this message]
2022-09-17 17:55 ` Eli Zaretskii
2022-09-17 18:04 ` Stefan Kangas
2022-09-18 7:52 ` Augusto Stoffel
2022-09-18 11:55 ` Philip Kaludercic
2022-09-18 12:38 ` Augusto Stoffel
2022-09-18 12:50 ` Philip Kaludercic
2022-09-18 13:30 ` Augusto Stoffel
2022-09-18 13:46 ` Philip Kaludercic
2022-09-18 19:38 ` Augusto Stoffel
2022-09-18 20:22 ` Philip Kaludercic
2022-09-18 21:18 ` Philip Kaludercic
2022-09-19 7:33 ` Augusto Stoffel
2022-09-19 8:03 ` Philip Kaludercic
2022-09-24 7:05 ` Augusto Stoffel
2022-09-24 8:01 ` Philip Kaludercic
2022-11-04 22:56 ` Philip Kaludercic
2022-09-18 11:58 ` Philip Kaludercic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkm=3v5TMyuMKnq-NDgWkOZRwJgKdcXjDn2t=LTfQc_sOMw@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=57884@debbugs.gnu.org \
--cc=arstoffel@gmail.com \
--cc=eliz@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).