The values of Emacs, the Neovim revolution, and the VSCode gorilla

Re:The values of Emacs, the Neovim revolution, and the VSCod... by signal11 on Sunday January 17, 2021 @12:04PM (#25812351)

> 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

[ Parent | on HN ]

Re:The values of Emacs, the Neovim revolution, and the VSCod... by slightwinder on Sunday January 17, 2021 @05:23PM (#25815771)

Those are very special and seems most of them are fixed/possible already?

[ Parent | on HN ]

Re:The values of Emacs, the Neovim revolution, and the VSCod... by signal11 on Monday January 18, 2021 @04:41AM (#25820003)

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

[2] https://github.com/microsoft/vscode/issues/14093

[ Parent | on HN ]

Re:The values of Emacs, the Neovim revolution, and the VSCod... by slightwinder on Monday January 18, 2021 @06:20AM (#25820597)

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?

[ Parent | on HN ]