Julien ÉLIE

I agree that shellcheck doesn't support zsh. My worry is that errors are triggered on all projects using Libtool. Such scripts are properly run by POSIX shells (like bash) and...

Hi Daniel, keeping the leading parenthesis in `(0)` is what the `pre-posix` dialect is expected to do. The intent of the proposal in #757 is exactly for that: doing no...

Oh yes, you're right. I kinda mix these two meanings as the only syntax change I noticed in the scripts I reformatted was these backticks. So maybe there could be...

OK, no problem, I understand your point. I was essentially suggesting it because some other widely-used reformatters do not change the syntax but only improve readability (like `perltidy` or `clang-format`,...

The empty line is also wrongly kept in statements (not only after `case...in`): ``` case "$x" in a) ;; b) ;; esac ``` is reformatted: ``` case "$x" in a)...

Indeed, all the modes remove backticks so the POSIX mode won't be of help. I am speaking of the stocked Bourne shell shipped with Solaris 10. Yes, I know it...

Sure, the default wouldn't change. The title of this feature request is "provide a way to disable all syntax substitutions", not making it the default. I don't know whether there...

Yes an `-ln=pre-posix` option would achieve that, indeed.

`PrePOSIX` looks good to me. Better be more generic than only `Bourne`. The point is that the option just reformats without applying any code modification.

Hi Daniel, FWIW I've just seen that the GNU Config project reverted last month the use of POSIX `$( )` with classic backticks to keep recognizing old machine types with...