Dirk MG Seynhaeve

I have the same issue: it seems like the parser is expecting a Simple Command, where we start with some assignments with local scope, followed by a command (word). However,...

We can't just move a directive to the first line of a file, if there is a shebang present (which *has* to be the first line, nay, the first characters...

If this is what you mean: ```if (first_line == (shebang || directive) then put_new_directive_on second_line else put_new_directive_on_second_line end ``` Maybe... What about: ``` skip_all_comment_lines at the start of the file();...

I have been impressed with the capabilities of the LanguageServer API: - The `Perl` extension makes for a very rich edit and debug experience based on the `Perl::LanguageServer` library (I...

> So I still don't understand what else could be made for the ShellCheck extension that is not already covered by Bash IDE or Bash Debug. I guess I was...

For the script I'm debugging right now, I can just disable my initialization. In my `.bashrc`, I return immediately if the Bash shell is invoked by the VS Code debugging...

I almost entered this as a new issue. I left it below as initially typed it up, to illustrate that this would indeed be nice to resolve... Feedback to @mvdan...

> I also don't think it would be a good idea in general; forcing backslashes would likely upset a good portion of the users. I'm not sure about that: formatting...

> The more formatting options the tool has, the harder it is to maintain, test, and use. Very good point on minimizing the command-line options! I even have the controversial...

> There is already a rule called `PSAlignAssignmentStatement` for that, which maps to the VSCode settting `powershell.codeFormatting.alignPropertyValuePairs` but it only applies to assignment statements in a hashtable or a DSC...