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…
Vim 8.0 is coming
71–80 of 420 posts
Re: Vim 8.0 is coming
#72To 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.
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.
Re: Vim 8.0 is coming
#73Earlier quoted context omitted.
I don't need to learn Qt Creator, Clion, xCode, AppCode and VS if I already know vim. Why I would to need to use a different text editor for each different language?
Unlike vim or emacs, you don't need to learn VS, Qt Creator, Clion or similar... Mostly, these tools are so intuitive, you just start being productive right after first time.
Re: Vim 8.0 is coming
#74I 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…
I became an heavy Emacs user as I could not find the comfort of Borland IDEs in UNIX, as I started to use it. Since I moved away from C++ into Java and .NET land, never felt the need to use them any longer. And nowadays, with Qt Creator, Clion, xCode, AppCode and VS, I also don't feel the need of them when I need to go back to C++. It is very good to know the basics from plain Vi, because there are still commercial U…
The great thing about Vi (and I presume Emacs as well) is that you can get keybindings for just about any IDE. I use Visual Studio for intellisense, but I install VsVim which gives it 90% of the most commonly used features of Vim. XCode has XVim. IntelliJ products have IdeaVim. I've used them all, they're all great. It's nice to be able to feel instantly at home in any editor.
Re: Vim 8.0 is coming
#75Earlier 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 recently switched to NeoVim and it really _does_ make a world of difference, saving is a whole lot faster when git-diff can be performed asynchronously and the ability to scan directories in the background makes fuzzy searching of files a lot faster.
Re: Vim 8.0 is coming
#76Earlier quoted context omitted.
I don't need to learn Qt Creator, Clion, xCode, AppCode and VS if I already know vim. Why I would to need to use a different text editor for each different language?
Unlike vim or emacs, you don't need to learn VS, Qt Creator, Clion or similar... Mostly, these tools are so intuitive, you just start being productive right after first time.
Re: Vim 8.0 is coming
#77And... 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…
(Source: Somewhere in :help, but unfortunately I can't find it right now.)
Re: Vim 8.0 is coming
#78Earlier 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.
Async I/O is not about disk I/O, but communication with other programs.
Re: Vim 8.0 is coming
#79Earlier quoted context omitted.
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!
To be fair, vim is not strictly vi although they were related. Amazing, I was 1 year old when both were started. How many other software package has such longevity? Unix and its various guises?
Re: Vim 8.0 is coming
#80With the age of their respective codebases, I'd love to know what lurks beneath? Immaculate, well factored code? A hornets nest of hacks - what do you expect from such old codebases - or have they been re-written so many times you'd never guess their ages from the codebase.