5 ms·

this async thing was Neovim's main selling point, right? I mean cruft-removal is all well and good but vim works fast and fine for me so not important. What doe

this async thing was Neovim's main selling point, right? I mean cruft-removal is all well and good but vim works fast and fine for me so not important. What does Neovim now offer that this doesn't?

jpambrun 10y ago
I think neovim just offered us VIM 8.0.
- baldfat 10y ago
  To be fair VIM developers have said they were all in the mix and coming. We even had Vim plug ins that pulled this off. So I really am not surprised.
dominotw 10y ago
'transform Vim into an embeddable text editor engine' I think that was the main objective of the project. Would be nice to real vim in IntelliJ idea.
- micku 10y ago
  This. And the scripting language I suppose?
- stephenboyd 10y ago
  As a naive IntelliJ user, I found myself editing files with Vim in IntelliJ's terminal console.
  - dominotw 10y ago
    whoa! had no idea this was thing .
  - weitzj 10y ago
    I was amazed when I discovered the console and everything works. I can launch vim, neovim and tig(nurses git front-end) from within IntelliJ and all shortcuts just work. Even fish shell in vi mode or tmux. So yeah, I have the shell running in IntelliJ with tmux enabled and launch tig inside of it.
tux1968 10y ago
Vim was in a virtual lock down of maintenance mode before Neovim came along and offered some competition. I'm happy to see Vim woken up out of its slumber, but let us not dismiss what Neovim offers or has already accomplished.
- flukus 10y ago
  The release history: https://en.wikipedia.org/wiki/Vim_(text_editor) https://en.wikipedia.org/wiki/Vim_(text_editor) doesn't looks pretty active to me.
  - flukus 10y ago
    Edit - I mean does look pretty active.
thomasahle 10y ago
Neovim is still a lot faster for me. A simple example is always commenting out a block <C-v>10jI#, which takes 5 seconds or so in vim (including 8.0), but is instant in neovim.
- 6502nerdface 10y ago
  The input sequence would be <C-v>10jI#<ESC> (I've just added escape at the end). I'm guessing the delay you are referring to is the delay imposed by your terminal emulator (not vim) to detect the Escape key at the end that terminates visual block mode. If I'm right, you can quickly press "j" just after you press ESC, which should cancel the ESC-detection delay and cause your comment characters to appear instantly. Edit: there's actually a few things that could be at play, including your terminal emulator, your screen/tmux (which is like another terminal editor, really), and vim's timeoutlen and ttimeoutlen settings.
  - philh 10y ago
    I wouldn't expect the terminal emulator or screen/tmux to cause a 5s delay in this situation; and if they did, I'd expect them to cause it in neovim as well as in vim.
    - cyphar 10y ago
      This does happen with neovim too. In fact, I had this issue in neovim even though I hadn't had it in vim. It was a one-line config change in my tmux.conf to fix it though, so no skin off my nose.
  - randlet 10y ago
    This is interesting! For me using <ESC> does indeed take a few seconds to complete commenting out the block. However, I have jk mapped to <ESC> and the commenting happens instantly using jk which makes sense in the context of your explanation.
    - hsitz 10y ago
cschmidt 10y ago
I believe it has a complete embedded terminal
- placeybordeaux 10y ago
  I've actually started using neovim as a default terminal paired with my standard shell. I personally never got that used to the commands for tmux or screen, and with neovim I get the exact commands I am expected as well as -send line to REPL- with https://github.com/kassio/neoterm https://github.com/kassio/neoterm
zem 10y ago
having lua as the native scripting language is pretty big too
- deleted 10y ago
  [deleted]
- vegabook 10y ago
  Lula would be proud ;-)

this async thing was Neovim's main selling point, right? I mean cruft-removal is all well and good but vim works fast and fine for me so not important. What does Neovim now offer that this doesn't?

jpambrun 10y ago

I think neovim just offered us VIM 8.0.

baldfat 10y ago
To be fair VIM developers have said they were all in the mix and coming. We even had Vim plug ins that pulled this off. So I really am not surprised.

dominotw 10y ago

'transform Vim into an embeddable text editor engine' I think that was the main objective of the project. Would be nice to real vim in IntelliJ idea.

micku 10y ago
This. And the scripting language I suppose?
stephenboyd 10y ago
As a naive IntelliJ user, I found myself editing files with Vim in IntelliJ's terminal console.
- dominotw 10y ago
  whoa! had no idea this was thing .
- weitzj 10y ago
  I was amazed when I discovered the console and everything works. I can launch vim, neovim and tig(nurses git front-end) from within IntelliJ and all shortcuts just work. Even fish shell in vi mode or tmux. So yeah, I have the shell running in IntelliJ with tmux enabled and launch tig inside of it.

tux1968 10y ago

Vim was in a virtual lock down of maintenance mode before Neovim came along and offered some competition. I'm happy to see Vim woken up out of its slumber, but let us not dismiss what Neovim offers or has already accomplished.

flukus 10y ago
The release history: https://en.wikipedia.org/wiki/Vim_(text_editor) https://en.wikipedia.org/wiki/Vim_(text_editor) doesn't looks pretty active to me.
- flukus 10y ago
  Edit - I mean does look pretty active.

thomasahle 10y ago

Neovim is still a lot faster for me. A simple example is always commenting out a block <C-v>10jI#, which takes 5 seconds or so in vim (including 8.0), but is instant in neovim.

6502nerdface 10y ago
The input sequence would be <C-v>10jI#<ESC> (I've just added escape at the end). I'm guessing the delay you are referring to is the delay imposed by your terminal emulator (not vim) to detect the Escape key at the end that terminates visual block mode. If I'm right, you can quickly press "j" just after you press ESC, which should cancel the ESC-detection delay and cause your comment characters to appear instantly. Edit: there's actually a few things that could be at play, including your terminal emulator, your screen/tmux (which is like another terminal editor, really), and vim's timeoutlen and ttimeoutlen settings.
- philh 10y ago
  I wouldn't expect the terminal emulator or screen/tmux to cause a 5s delay in this situation; and if they did, I'd expect them to cause it in neovim as well as in vim.
  - cyphar 10y ago
    This does happen with neovim too. In fact, I had this issue in neovim even though I hadn't had it in vim. It was a one-line config change in my tmux.conf to fix it though, so no skin off my nose.
- randlet 10y ago
  This is interesting! For me using <ESC> does indeed take a few seconds to complete commenting out the block. However, I have jk mapped to <ESC> and the commenting happens instantly using jk which makes sense in the context of your explanation.
  - hsitz 10y ago

cschmidt 10y ago

I believe it has a complete embedded terminal

placeybordeaux 10y ago
I've actually started using neovim as a default terminal paired with my standard shell. I personally never got that used to the commands for tmux or screen, and with neovim I get the exact commands I am expected as well as -send line to REPL- with https://github.com/kassio/neoterm https://github.com/kassio/neoterm

zem 10y ago

having lua as the native scripting language is pretty big too

deleted 10y ago
[deleted]
vegabook 10y ago
Lula would be proud ;-)