If, like me, you find yourself trying to use shellcheck to lint .zsh files with #!/bin/zsh but it keeps telling you:

shellcheck: error
error 
ShellCheck only supports sh/bash/dash/ksh scripts. 
Sorry! [SC1071]

What I was able to do is pass the --shell=bash argument to shellcheck and then it would lint my files.

In my case this was configured in my SublimeLinter config, like so:

{
    "linters": {
        "shellcheck": {
            "args": [
                "--shell=bash"
            ]
        },
    }
}

…just in case you are using Sublime Text!

In case you’re wondering what’s easier:

1. Writing CLI tools e.g. shell scripts + zsh plugins
2. Writing CLI tools using PHP e.g. symfony/console, PHP-CLI, etc

#2 is harder. I tried it over the weekend.

I went through the key-bindings in Micro (which use different modifier keys) and added them to Sublime Text:

    { "keys": ["ctrl+s"], "command": "save", "args": { "async": true } },
    { "keys": ["alt+up"], "command": "swaplineup" },
    { "keys": ["alt+down"], "command": "swaplinedown" },
    { "keys": ["ctrl+left"], "command": "bol" },
    { "keys": ["ctrl+right"], "command": "eol" },
    { "keys": ["ctrl+o"], "command": "prompt_open" },
    { "keys": ["ctrl+z"], "command": "undo" },
    { "keys": ["ctrl+y"], "command": "redo" },
    { "keys": ["ctrl+c"], "command": "copy" },
    { "keys": ["ctrl+x"], "command": "cut" },
    { "keys": ["ctrl+d"], "command": "duplicate_line" },
    { "keys": ["ctrl+v"], "command": "paste" },
    { "keys": ["ctrl+a"], "command": "select_all" },
    { "keys": ["ctrl+b"], "command": "toggleterminuspanel" },
    { "keys": ["ctrl+q"], "command": "close" },
    { "keys": ["ctrl+up"], "command": "move_to", "args": { "to": "bof" } },
    { "keys": ["ctrl+down"], "command": "move_to", "args": { "to": "eof" } },
    { "keys": ["alt+backspace"], "command": "deleteword", "args": { "forward": false, "subwords": true } },
    { "keys": ["ctrl+f"], "command": "show_panel", "args": { "panel": "find", "reverse": false } },
    { "keys": ["alt+shift+f"], "command": "showpanel", "args": { "panel": "findin_files" } },
    { "keys": ["ctrl+t"], "command": "showoverlay", "args": {"overlay": "goto", "showfiles": true} }, // Hurts transpose, but never use.
    { "keys": ["ctrl+e"], "command": "showoverlay", "args": {"overlay": "commandpalette"} },

If you’ve been following along with my Vim/Modal editing debacle, here’s where I’ve landed.

——–

I’m a all-or-nothing person, so since I can’t do modal editing everywhere (without madness) I’m ditching the paradigm

I’ve been playing around with using nano this morning for e.g. Git commits, etc and decided to use micro instead.

Micro is a great editor after-all. Checkout the customizations I’ve made to it to make it more useful:

.config/micro/settings.json

.config/micro/bindings.json

I’m also going to work to have parity with Sublime, here’s what I have so far:

Packages/User/Default (OSX).sublime-keymap#L66.sublime-keymap#L66)

I’m going to start trying to improve my editing techniques in normal editing across my system instead of spamming the GUI menu and sloppy ⌘- combos to get more and more efficient at editing in macOS.

How do Vim’mers deal with the frustration of not being able to edit text (like the one I’m writing, here, on dev.to) everywhere else (outside of e.g. Vim) using modal editing?

I’m not really liking that, yeah, I can get the benefit from modal editing and in Sublime Text (due to e.g. Vintage) but not anywhere else without having to go way-out-there and use something like cknadler/vim-anywhere.

I feel like it might not be worth it to learn a new paradigm if I can’t use it in more places.

Annoyingly, I’ve disabled Vintage for now. I might even consider using e.g. micro for text editing in my terminal.