Editors (Vim)

#1

Post by Austin_Conlon » Sat, Jun 06, 2020, 2:51 AM UTC

Editors (Vim)
missing.csail.mit.edu

Re: Editors (Vim)

#2

Post by jedwards1211 » Sat, Jun 06, 2020, 2:59 AM UTC

Vim emulation in VSCode worse than any other IDE I've used.

All extensions have to run on the same thread in a background process and intercepted keystrokes are passed to that process over IPC. So if other extensions (like the TS language tools) are tying up the extension host process, the Vim extension can't respond to your keyboard input until other extensions yield.

Performance issues come and go but for awhile I was stuck waiting for several seconds any time I typed a A lot of us have tried to demand a separate process for extensions that intercept keystrokes to solve this issue permanently. But the maintainers don't really care.

Re: Editors (Vim)

#3

Post by vulcan01 » Sat, Jun 06, 2020, 3:09 AM UTC

I feel like it would be far more useful to just talk about vimtutor. At least for me, it was the only way I was able to grok vim.

Re: Editors (Vim)

#4

Post by tazard » Sat, Jun 06, 2020, 3:20 AM UTC

jedwards1211 wrote: post #2

Vim emulation in VSCode worse than any other IDE I've used. All extensions have to run on the same thread in a background process and intercepted keystrokes are passed to that process over IPC. So if other extensions (like the TS language tools) are tying up the extension host process, the Vim extension can't respond to your keyboard input until other extensions yield. Performance issues come and go but for awhile I…

This makes so much sense. Thanks for explaining that.

Re: Editors (Vim)

#5

Post by lawn » Sat, Jun 06, 2020, 3:20 AM UTC

jedwards1211 wrote: post #2

Vim emulation in VSCode worse than any other IDE I've used. All extensions have to run on the same thread in a background process and intercepted keystrokes are passed to that process over IPC. So if other extensions (like the TS language tools) are tying up the extension host process, the Vim extension can't respond to your keyboard input until other extensions yield. Performance issues come and go but for awhile I…

I don't use it myself but it's possible to embed Neo Vim in VSCode. So you're able to use edit text using a real instance instead of relying on a crappy emulation.

Re: Editors (Vim)

#6

Post by wildrhythms » Sat, Jun 06, 2020, 3:20 AM UTC

jedwards1211 wrote: post #2

Vim emulation in VSCode worse than any other IDE I've used. All extensions have to run on the same thread in a background process and intercepted keystrokes are passed to that process over IPC. So if other extensions (like the TS language tools) are tying up the extension host process, the Vim extension can't respond to your keyboard input until other extensions yield. Performance issues come and go but for awhile I…

I use VS Code w/ vim mode for NodeJS/Angular/React development and haven't noticed performance issues; granted, I'm running on a beefy Windows PC since it's the only good option I've found for vim on Windows.

On Mac/Linux I just use neovim with coc[1], which works beautifully.

[1] https://github.com/neoclide/coc.nvim

Re: Editors (Vim)

#7

Post by chongli » Sat, Jun 06, 2020, 3:22 AM UTC

jedwards1211 wrote: post #2

Vim emulation in VSCode worse than any other IDE I've used. All extensions have to run on the same thread in a background process and intercepted keystrokes are passed to that process over IPC. So if other extensions (like the TS language tools) are tying up the extension host process, the Vim extension can't respond to your keyboard input until other extensions yield. Performance issues come and go but for awhile I…

As a long time vim user, I’ve tried VSCode a few times and I cannot for the life of me figure out what all the hype is about. Can anyone who is proficient with it explain the philosophy behind it and what makes it so great? This is a sincere question, not a rhetorical one.

Re: Editors (Vim)

#8

Post by moonchild » Sat, Jun 06, 2020, 3:22 AM UTC

> no matter what shell you use, you can export EDITOR=vim

Nit: in csh, it's 'setenv EDITOR vim'

Re: Editors (Vim)

#9

Post by ima_banana » Sat, Jun 06, 2020, 3:24 AM UTC

Has eye-tracking been explored for improved code editing beyond Vim?

Vim does away with the hand-travel delays, but many of these ninja keystroke moves to navigate code are just what your eyes do already (but not all, such as the search function).

Re: Editors (Vim)

#10

Post by fstarship » Sat, Jun 06, 2020, 3:29 AM UTC

lawn wrote: post #5

jedwards1211 wrote: post #2

Vim emulation in VSCode worse than any other IDE I've used. All extensions have to run on the same thread in a background process and intercepted keystrokes are passed to that process over IPC. So if other extensions (like the TS language tools) are tying up the extension host process, the Vim extension can't respond to your keyboard input until other extensions yield. Performance issues come and go but for awhile I…

I don't use it myself but it's possible to embed Neo Vim in VSCode. So you're able to use edit text using a real instance instead of relying on a crappy emulation.

I am not entirely sure if you are referring to https://marketplace.visualstudio.com/items?itemName=asvetlia...

I just switched after using vs vim and got much better performance.

I had neovim installed anyway for the EX commands