Isaac Oscar Gariano

> it's not inconsistent if you consider that your backslash in the > comment line is redundant. That is, this also works: > > echo hello \ > # comment...

I've updated some of the recommended extensions, and added a new commit that autoformats rust, python, and fish code on save. (Only VS Code users will benefit from those, as...

I've added a new commit that makes some of the settings only apply to specific folder, to match the `.editorconfig` and `build_tools/style.check`. Importantly, the fish files in `tests` will no...

> Consider adding fish-lsp to the recommended extension list. I tried that (`ndonfris.fish-lsp`), as well as `gio00.fish`, `skyapps.fish-vscode`, and `lunaryorn.fish-ide`, they incorrectly highlight strings, e.g. ```fish echo \"hello world ```...

> yes, I'd prefer that over an editor-specific solution. Maybe we should call it "fish_indent: on/off", to match clang-format Maybe with a `#!` instead of just a `#`, indicating it's...

> It's a pre-order AST traversal, so we can always do "check any (not yet checked) comments until the start of the current node" to find the directives that apply...

> This is an incredibly trivial issue, but open an interactive fish > and type `echo \`. > Before you press enter, the `\` will be coloured with `fish_color_error`. >...