Live data from Hacker News

NeoVim 0.2.0 released

github.com

131–140 of 141 posts

Re: NeoVim 0.2.0 released

#131
post #83

Earlier quoted context omitted.

I tried jumping boat to nvim something like a year ago. One of my plugins ran into an issue, so I came back. A better question for us "old-vimers" is not "is nvim stable, because I'd like something modernized", but rather "what does nvim have that vim doesnt". I'm actually asking. My short glance led me to believe that it's got two things going for it: a) smoother interop with other "modern" tools b) cleaned up codeb…

The major reason I use neovim is because with the addition of :terminal command I no longer need to remember tmux commands and with the add-on neoterm I have a one button command to send the current selection (or line) to whatever terminal I please. This means that when developing code in any language that has a REPL I can test it out as I develop line by line.

I've been looking for something like this in vim for a while (something like Emacs + ESS). I've found a few plugins and workarounds using tmux, but nothing as smooth as you said. I'll try it out.

Re: NeoVim 0.2.0 released

#132
post #83

Earlier quoted context omitted.

I tried jumping boat to nvim something like a year ago. One of my plugins ran into an issue, so I came back. A better question for us "old-vimers" is not "is nvim stable, because I'd like something modernized", but rather "what does nvim have that vim doesnt". I'm actually asking. My short glance led me to believe that it's got two things going for it: a) smoother interop with other "modern" tools b) cleaned up codeb…

I switched to neovim for faster syntax checking with Neomake. Syntastic with vim was unusably slow. I don't know if anything has improved with vim since (probably, with 8.0), but I have no reason to go back, either.

I got frustrated with how slow syntastic was too, but I have just upgraded 8.0 and have switched to using https://github.com/w0rp/ale for asynchronous linting and it's working very well.

Re: NeoVim 0.2.0 released

#133
post #129

My first impression was not a good one. Its hardwired assumption of xterm control sequences, even when TERM says something else entirely, caused it to be unusable on my terminal (which understands DECSLPP as DECSLPP). * https://github.com/neovim/neovim/blob/v0.2.0/src/nvim/tui/tu...

So, what terminal do you use?

Re: NeoVim 0.2.0 released

#134

Earlier quoted context omitted.

> The main reason NeoVim exists at all is because Bram Moolenaar refused to accept any patches for async support. People already did the work for him and he didn't want it. This is not true. If the work was not complete and not as how the lead maintainer/developer wants it. It is highly unlikely that it would be merged. I suggest you actually go and read the mailing list when this happened. I have seen it.

If I remember correctly, the guy kept changing his patch to meet Bram's conditions, but then Bram kept adding more requirements, to the point where it seemed like Bram was just making up excuses for not accepting the patch. I could be wrong though. Please can you link the mailing list. (I can't find it) I'll read it and take back what I said, if that is the case. Edit: spelling

This thread is basically over already, but here's a few links to what I think are relevant messages from the discussion (And from these links you can largely see the whole thing, though there's a few other threads spread out elsewhere):

https://groups.google.com/d/msg/vim_dev/-4pqDJfHCsM/rTnUuZTg...

https://groups.google.com/d/msg/vim_dev/-4pqDJfHCsM/skO2ee5k...

Personally the last post is the most important. He's basically saying that he knows there's clearly problems with his patch, but that he doesn't want to work on it until Bram takes the time to look at it and tell them what's wrong. He wants to push it in even though it's not 100% functional, to the point that he suggests merging it and calling it "experimental-timers".

The above isn't 100% related to Neovim, but below is the thread where Thiago Arruda essentially decides to create Neovim, and the other thread is brought up in this one which is why it is relevant:

https://groups.google.com/forum/#!searchin/vim_dev/Tarruda%7...

https://groups.google.com/d/msg/vim_dev/65jjGqS1_VQ/VBLymmdW...

I recommend looking at the dates, Thiago posted the concept patch 12/4/13, and Christian ZyX responded 5 days later, and then Thiago responds that he's done working on the patch because of a list of reasons: One being he has heard stories of long response times from the Vim developers, Two being that 5 days was too long of a response time and that Bram hasn't responded to his patch, Three being that it was too complicated and he wouldn't be able to make it work, and Four being that he didn't want to work on it if it wasn't guarantee to ever get into Vim.

Let me know if there's a problem with the links.

Re: NeoVim 0.2.0 released

#136
post #47

Earlier quoted context omitted.

Close, but not enough. I want to open the same editor session spread across multiple windows on multiple monitors.

I saw this thread, and I promised myself I wasn't going to plug Kakoune -- I think NeoVim is a great project and I want it to succeed. They deserve every bit of the praise they're getting. But I'm going to have to break my promise, because Kakoune has the exact feature you're after, and I'm using it right now. That, along with familiar keybindings, selection-oriented modal interface, tmux integration... I could go on…

I do depend on a completion plugin, other than that it might just work. I'll have a look at it - thanks for the suggestion! Did not know it existed.

Re: NeoVim 0.2.0 released

#137
post #35
post #25

Earlier quoted context omitted.

Honestly for me the main reason was that it finally has builtin `:terminal`. The plugins for use with vim have always been slightly buggy for me.

Can you please elaborate how you make use of the built in terminal emulation of neovim? Whenever I see a mention I think "neat" but have yet to integrate it into my workflow.

I use it to either run microservices for testing, or for testing code in the erlang shell. It's MUCH easier to copy and paste inside vim and be able to copy logs out into a buffer to run sed expressions on it, than if I were using another terminal.

Re: NeoVim 0.2.0 released

#138

Earlier quoted context omitted.

Being "stuck in a GUI mental model" means I use IDEs for most development I do instead of vim/emacs (which I guess would be the extreme of being stuck in that model?). At the end of the day using my mouse to open a file doesn't impede my ability to code in the slightest. I've never understood the almost subtle elitism behind being able to use Vim without a mouse because "moving your hand to the mouse is slow". If a p…

It's not about elitism, it's about using the tool you've chosen efficiently. If I used the IDEs you use, and you suggested to me a way of using them more efficiently, I wouldn't accuse you of elitism. I'd thank you for showing me something new and improving the way I work. Have you ever witnessed somebody using a mouse to move between form fields? My bet is you at least thought about telling them they can use the tab…

Have you used a PDF form where the order of the fields is wrong so Tab moves all over the place? I sure have. There is no silver bullet.

Re: NeoVim 0.2.0 released

#139
post #133
post #129

My first impression was not a good one. Its hardwired assumption of xterm control sequences, even when TERM says something else entirely, caused it to be unusable on my terminal (which understands DECSLPP as DECSLPP). * https://github.com/neovim/neovim/blob/v0.2.0/src/nvim/tui/tu...

So, what terminal do you use?

I use several. But this particular one is most definitely not xterm, nor dtterm.

Ironically, it actually implements both of DECSLPP and DECSCPP, but without the restrictions to only some sizes. So nvim could use these DEC VT control sequences to set the screen size. Unfortunately, there is no simple mechanism for nvim to know this. There's no terminal type that a user could set that would hint at this ability, let alone a termcap/terminfo capability.

Nonetheless, just blithely assuming that every terminal type in existence implements dtterm's idiosyncratic extensions to the DEC VT control sequence set is wrong. There is a way for nvim to be told that the terminal is likely to have dtterm's idiosyncrasies, or indeed xterm's. nvim even uses it to detect other terminal types with other idiosyncratic control sequence extensions.

It actually becomes usable once this bug is fixed.

* https://github.com/jdebp/neovim/commit/3304de142b60efe8728c0...

Re: NeoVim 0.2.0 released

#140
post #101

The only thing that bugs me about neovim is that it seems to require workarounds to get the escape button to behave the same as in vim. When I press escape to exit insert mode, there is a small delay. If I press a key (e.g. 'j' to go down) too quickly after Escape, it inserts the 'j' and cancels what escape is meant to do. In tmux I know of a workaround (iirc, 'set escape-delay 0' or something similar), but I wish I…

Have tried the newest version? I couldn't reproduce this delay.

And btw. it's version 0.2 not 2.0

Post reply on HN