Live data from Hacker News

Vim 8.0 is coming

github.com

91–100 of 420 posts

Re: Vim 8.0 is coming

#91
post #5

By the way, I have a question: what is the best learning material for intermediate/advanced Vim users? I know quite a lot of Vim features but apart from vimtutorial, I never learned them in any organized way - it was more of a bunch of tricks I found via googling. It would be nice if there was a book (preferably free) on this editor.

:h usr_toc is really one of the best introductions to vim (after vimtutor), I am surprised that not that many people seem to know about it.

Get a pdf of it here: http://www.eandem.co.uk/mrw/vim/usr_doc/.

Re: Vim 8.0 is coming

#92

And... there goes a lot of energy to neovim. The only other feature request I have is expanded features for window drawing for plugin makers. I want to be able to draw over a buffer without editing the text. If you've ever used jedi-vim, you'll see the function's signature appear above the line you're editing. What a lot of people don't realize is that is actually modifying the file and saving the prior contents of t…

From what this initial view of Vim 8.0 looks, it actually went in the direction of Neovim, the asynchronous inner works were what made me try Neovim in the 1st place. Now, from what I can understand, Neovim only has two advantages, a cleaner code trough re-writing (it's debatable if that's really an advantage) and the ability of using other languages for plugins (which seems clearly and advantage due to the lacking f…

Don't forget true color support for those sweet colorschemes!

Re: Vim 8.0 is coming

#93
post #88

I alternate between Emacs and Vim every 5 years or so. Emacs gave me superior customizability using a "real" programming language: elisp. Vim, on the other hand, offers a faster, more efficient editing UX. The older I get, the wider the spread becomes between the speed of my thought and the rate at which I can input editing commands into the terminal. Vim allows me achieve higher efficiency and to almost "think ahead…

You may want to consider looking at Evil mode, which gives you a very close approximation to the vim editing bindings in emacs. I've been using it as part of the spacemacs distribution for a while now and find it to be the best of both worlds.

Re: Vim 8.0 is coming

#94

Is there a way how I can copy blocks of code outside the vim window to another application without also copying the line numbers? Also is there one simple key combination to [un]comment a line or a selected block? I found out how to do many simple operations with this ancient tool, what can be really fun if you have nothing else funny in life (too many people have no other sources of fun, really) - but I am still not…

    vnoremap  "+y

Re: Vim 8.0 is coming

#95
post #4

I have vim, neovim and emacs (and spacemacs) installed. Right now I'm trying to get into emacs a bit more. What's interesting to me, and the reason I try to keep up to date with the latest changes for all four editors, is that it's been now, what, 25 years (?) since emacs and vim started "competing" and they still are. I guess we could be saying the same in 10 years about firefox and chrome, but it still is amazing i…

According to Wikipedia ( https://en.wikipedia.org/wiki/Vi and https://en.wikipedia.org/wiki/Emacs ) both vi and Emacs are from 1976. 40 years this year!

vi is not Vim.

Re: Vim 8.0 is coming

#96
post #37

Earlier quoted context omitted.

:set nonumber removes the line numbers so you can copy without them

no, i do not want to disable line numbering. I want to avoid to copy them. I do not want to switch line numbering on off for every copy process. Absurd idea.

A better option would be to use a plugin that yanks text to the system clipboard.

Re: Vim 8.0 is coming

#97

Earlier quoted context omitted.

Async I/O, plus JSON is seriously enormous. I'm very excited for how much faster things will be, and I can imagine JSON support will definitely make integration just that much easier. My one minor gripe was plugin speed, as syntax highlighting, linting, etc. can take long enough to be jarring.

Async I/O? In a text editor , where the bulk of the time is spent waiting for the user to do something? I've used (an older version of) Vim on huge 100MB+ files and never thought it to be slow at all. In fact I don't think I've ever experienced any lag with Vim. I suspect you won't find this new version any faster.

I've opened 5GB files in Vim, on an average 2010 Ubuntu desktop. It took some time, like 5 minutes, but it worked.

Re: Vim 8.0 is coming

#98
post #93
post #88

I alternate between Emacs and Vim every 5 years or so. Emacs gave me superior customizability using a "real" programming language: elisp. Vim, on the other hand, offers a faster, more efficient editing UX. The older I get, the wider the spread becomes between the speed of my thought and the rate at which I can input editing commands into the terminal. Vim allows me achieve higher efficiency and to almost "think ahead…

You may want to consider looking at Evil mode, which gives you a very close approximation to the vim editing bindings in emacs. I've been using it as part of the spacemacs distribution for a while now and find it to be the best of both worlds.

Evil mode is slower than vim. And also you are in evil mode only during the editing phase. All other menus drop you back to default emacs keybindings and that is very painful experience. I used evil mode for a couple of years and still just went back to vim.

Re: Vim 8.0 is coming

#99

To list few of the new features: Asynchronous I/O support, channels (Vim can now exchange messages with another process in the background asynchronously), Background jobs, timers, packages for plugins! Wow! This is huge. So many interesting features landing on Vim 8.0.

> Asynchronous I/O support

I don't keep myself much up to date on these things, but wasn't this one of the main new features in NeoVim? (then code cleanup, then more language to script in)

Re: Vim 8.0 is coming

#100
post #25

Earlier quoted context omitted.

If I want to put parens around a word I do, ciw() P (change word pulls it into the default register, insert the parens and then paste from the register back between the parens). You can use the same pattern for any selection you have visually highlighted, such is the wonderful power of vim.

Nice use of the buffer. Is there a nice hack to remove the parentheses around a word as well?

ca( would work for this as well.
Post reply on HN