3 ms·

I don’t find VS Code to be a good text editor in the sense of a tool to wrangle text: the keyboard shortcuts are rather arbitrary and don’t seem to be logically

I don’t find VS Code to be a good text editor in the sense of a tool to wrangle text: the keyboard shortcuts are rather arbitrary and don’t seem to be logically organised, and it seems not to have learnt much from eg modern text editors like Sublime Text (even Sublime compatibility isn’t as good as the real thing). That said, for writing code, it’s fine because most of the time I’m thinking and typing in short runs of text. I’d love for it to receive a bit of love so it’s a better at wrangling text out-of-the-box, however.

qsort 6y ago
I completely share your sentiment. VSCode is by far my favorite programming environment, its killer features as far as I'm concerned are its excellent debugging functionality and the remote mode (we often work on multiple remote machines simultaneously -- being able to have ad-hoc remote configs is a life-saver!) The worst part is, ironically, the editor itself. As a former vim user I'd love to have vim keybindings, but the vim extensions are painfully slow and unresponsive. I ended up just using the default in spite of it being incredibly mediocre.
- busrf 6y ago
  Have you tried the vscode-neovim (https://github.com/asvetliakov/vscode-neovim https://github.com/asvetliakov/vscode-neovim) extension? It uses an instance of neovim to provide the vim behaviour rather than emulating it, and I’ve found it to be more responsive than VsCodeVim.
slightwinder 6y ago
Shortcuts in VS Code are a setting. Just load which shortcut-setup you prefer. That's pretty normal with good dev-tools nowadays, because everyone has different preferences and habits.
- signal11 6y ago
  > Shortcuts in VS Code are a setting. Just load which shortcut-setup you prefer. There are quite a few shortcuts that cannot be implemented due to missing capabilities in VS Code. For example -- this list from an author of a VS Code plugin that emulates Sublime[1]. [1] https://github.com/Microsoft/vscode/issues/3776 https://github.com/Microsoft/vscode/issues/3776
  - slightwinder 6y ago
    Those are very special and seems most of them are fixed/possible already?
    - signal11 6y ago
      Only a few of them are done. The others are marked essentially closed wontfix ("To keep the number of issues in our inbox at a manageable level, we're closing issues that have been on the backlog for a long time")[1] or "write an extension for this"[2]. The bigger issue, which is lost in this forest of Github issues, is that VS Code needs a good hard look at its keyboard and text processing model. [1] https://github.com/microsoft/vscode/issues/14028 https://github.com/microsoft/vscode/issues/14028 [2] https://github.com/microsoft/vscode/issues/14093 https://github.com/microsoft/vscode/issues/14093
      - slightwinder 6y ago
        True, but those are still exotic edge-cases. In terms of shortcut-ability VS Code plays in the top on par with emacs, vim and KDE. You are complaining about the missing 0.1%, not something like >50% of lacking features. Also, your original complain was that the shortcuts are "arbitrary and don’t seem to be logically organised". This can be fixed by loaading which ever organisation-scheme you prefer. So your actual complain is, it does not match your habits out-of-the-box?

qsort 6y ago

I completely share your sentiment. VSCode is by far my favorite programming environment, its killer features as far as I'm concerned are its excellent debugging functionality and the remote mode (we often work on multiple remote machines simultaneously -- being able to have ad-hoc remote configs is a life-saver!) The worst part is, ironically, the editor itself. As a former vim user I'd love to have vim keybindings, but the vim extensions are painfully slow and unresponsive. I ended up just using the default in spite of it being incredibly mediocre.

busrf 6y ago
Have you tried the vscode-neovim (https://github.com/asvetliakov/vscode-neovim https://github.com/asvetliakov/vscode-neovim) extension? It uses an instance of neovim to provide the vim behaviour rather than emulating it, and I’ve found it to be more responsive than VsCodeVim.

slightwinder 6y ago

Shortcuts in VS Code are a setting. Just load which shortcut-setup you prefer. That's pretty normal with good dev-tools nowadays, because everyone has different preferences and habits.

signal11 6y ago
> Shortcuts in VS Code are a setting. Just load which shortcut-setup you prefer. There are quite a few shortcuts that cannot be implemented due to missing capabilities in VS Code. For example -- this list from an author of a VS Code plugin that emulates Sublime[1]. [1] https://github.com/Microsoft/vscode/issues/3776 https://github.com/Microsoft/vscode/issues/3776
- slightwinder 6y ago
  Those are very special and seems most of them are fixed/possible already?
  - signal11 6y ago
    Only a few of them are done. The others are marked essentially closed wontfix ("To keep the number of issues in our inbox at a manageable level, we're closing issues that have been on the backlog for a long time")[1] or "write an extension for this"[2]. The bigger issue, which is lost in this forest of Github issues, is that VS Code needs a good hard look at its keyboard and text processing model. [1] https://github.com/microsoft/vscode/issues/14028 https://github.com/microsoft/vscode/issues/14028 [2] https://github.com/microsoft/vscode/issues/14093 https://github.com/microsoft/vscode/issues/14093
    - slightwinder 6y ago
      True, but those are still exotic edge-cases. In terms of shortcut-ability VS Code plays in the top on par with emacs, vim and KDE. You are complaining about the missing 0.1%, not something like >50% of lacking features. Also, your original complain was that the shortcuts are "arbitrary and don’t seem to be logically organised". This can be fixed by loaading which ever organisation-scheme you prefer. So your actual complain is, it does not match your habits out-of-the-box?