David Vo

This is ESLint autofixable, so will show up as a quick fix in VSCode. I'd love to know how to make autoimport do the right thing though. We currently don't...

I'm not really sure the questions are addressable in any straightforward manner. There's also (unsurprisingly) a lot of merge conflicts by this point, so needs a rebase. Happy for someone...

Damn, how did we miss this one

Yikes. I'd be inclined to do two things: - Add to the docs, as suggested. - Detect the missing support for `--extensions-dir` somehow. I'm not sure how hard this would...

Weird, I wasn't expecting an auto update to a prettier alpha.

I don't see where our eslintrc extends typescript-eslint/recommended. Maybe we have a whole bunch of lints and we just haven't noticed :eyes:

It'll probably be easy to build a POC for the `take` action using the Vim/Neovim extension.

I believe both extensions allow for mapping keybindings to complex VSCode commands. I think with the Vim extension you'd have to modify your `keybindings.json`? You can match vim modes though....

On a related note, when poking around to see whether there's a decent Kakoune mode for VSCode, I found the [ModalKeys extension](https://github.com/haberdashPI/vscode-modal-keys) which might be interesting. In particular: > The...

Found this in a GitHub search for helix, looks like it wouldn't have the same issue: https://github.com/DCsunset/vscode-modal-editor