Live data from Hacker News

Vim 8.0 released

groups.google.com

201–210 of 308 posts

Re: Vim 8.0 released

#201
post #8

Given the occasion, and given that vim is charity-ware software ( http://charityware.info/ ), it would be cool to have some sort of HN-wide donation to ICCF ( http://iccf-holland.org/ ). Donation page: http://iccf-holland.org/donate.html It seems that you can send bitcoins too: http://iccf-holland.org/bitcoin.html Imho just mentioning HN in the payment description would be okay :)

Given Vim powers our industry, it'd be neat if pg or any of the other big members of our community donated a non-trivial amount. There is very few pieces of software I could never imagine replacing in my toolkit. Linux? I use Windows, too. GCC? Clang gets some love sometimes. Languages themselves? I'm fluent in several. Shell? I used Bash for years, now I switched to ZSH, but could go back to Bash if I needed. Tmux?…

I came into Vim pretty happy with my other tools (a very-enhanced Sublime Text 3 and JetBrains IDEs)...I wasn't trying to learn Vim, I just had to. Vim is now basically my one tool. That and tmux...and more of the stuff I was using tmux's features for I'm doing in Vim. Both tools are definitely irreplaceable for me at this point, but vim much more than the other.

Re: Vim 8.0 released

#202
post #179

Earlier quoted context omitted.

nvi definitely provides more features than the original vi, just not nearly as much as vim. And it doesn't have a comparable ecosystem of plugin/package developers around it, either.

Is there a popularity dashboard of plugins that one could check to see what features vim users are enjoying that I've been living without?

For a conservative list of "essential plugins", see https://www.vi-improved.org/plugins/

"surround" and "targets" are indispensable for me.

Re: Vim 8.0 released

#203
post #69

Thanks for the work done here. I'm not a VIM user anymore (I use Spacemacs now), but it opened my eyes/mind to what is a professional code editor. After using VIM, using any other editor feels like programming in Notepad. VIM you'll always be in my heart.

How did you learn Spacemacs? I'm still using vim but would like to try & learn Spacemacs. What's a good way to learn it?

I just dove in about six months ago, and now I feel v productive in Spacemacs. The Spacemacs ABC videos are helpful.

Three of Spacemac's four pillars (mnemonic, discoverable, consistent) make it relatively easy to get the hang of. My early usage looked something like:

- Think of task I want to accomplish that probably has key binding

- Begin typing SPC -

- If that doesn't work, type SPC-: and begin typing what I think the command might be called

- If that doesn't work, search web for "Spacemacs key binding "

- If that doesn't work, find/read relevant Spacemacs layer documentation

- If that doesn't work, ask in the Spacemacs gitter channel

- Memorize key binding

Once I learned a binding I found it easy to remember due to the mnemonicness:

open this file in Github? SPC-g-h-o of course (g (git) - h (..hub) - (open))

view most recent search buffer? SPC-s-l (s (search) - l (last search buffer))

maximize this window's buffer? SPC-w-m, etc

Re: Vim 8.0 released

#204
post #11

I moved to http://wikemacs.org/wiki/Evil and I am happy with the transition. Spacemacs seems to be a good choice nowadays. Magit and org-mode are worth it.

I'm a big fan of evil-mode as well, though for some things they can't decide if they want to be just like vim or not (One example is whether or not yanking to the default register goes to the clipboard).

For me yanking with `y` copies to my system clipboard. I'm pretty sure this has nothing to do with evil; I think it's an emacs setting. Perhaps one of these?

    (setq select-enable-clipboard t)
    (setq select-enable-primary t)
See https://www.gnu.org/software/emacs/manual/html_node/emacs/Cl...

Re: Vim 8.0 released

#205

Earlier quoted context omitted.

Kill region, save, run/compile/read, undo if needed. With undo tree (or if you add commit to the process above) there is no need to comment just one region to turn off something. Optionally, convert the region into a separate function/method and just don't call it while checking.

You still didn't explained why it wasn't a good practice. This just sounds impractical.

Commented code (as in, working code commented out, not comments in code) eventually rots/becomes cruft that at some point in time is going to bite you (or someone else in your team, or some maintainer in the future)

Re: Vim 8.0 released

#206
post #141

Earlier quoted context omitted.

It's close, but I think NeoVim's RPC model could be huge. Writing a new frontend for vim no longer seems that crazy of a goal which makes it easier for people to experiment with new editor ideas while relying on the very solid core of vim (well at least I find that exciting, idk if the general vimmer cares).

I dream of the day that when you tick off "vim binding" in the settings of any IDE it loads neovim for controlling the buffer.

Or rather, a day where its easier, more flexible, and more performant for IDEs to always(only) use an embedded neovim. Getting plugin support "for free".

The keybindings would then be the only thing that the IDE changes.

Re: Vim 8.0 released

#207

Earlier quoted context omitted.

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

The input sequence would be 10jI# (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'…

You can also add this to your .vimrc:

  set noesckeys

Re: Vim 8.0 released

#208

Earlier quoted context omitted.

You still didn't explained why it wasn't a good practice. This just sounds impractical.

Yeah, "not a good practice" (i.e. "the user is wrong" or "why would you want to do that?") is the lazy way of justifying software deficiencies.

I use emacs, so deficiencies on how vim handles anything do not mean much to me, actually.

Re: Vim 8.0 released

#209
post #145

Earlier quoted context omitted.

I use tmux + vim on my Macbook and it runs really well! (vim built from MacPorts).

Have you tried tmux + neovim yet though? It's way faster and smoother in just about every aspect I can think of. Strongly recommend it.

I haven't but I've never had vim perform anything slower than perceptively instant. Even on the lowest of specification virtual machines and servers I've installed it on.

I'm not sure how, in my use case, neovim could improve upon vim. vim's fast, available virtually everywhere, packaged with many OS's and distros, and has a rich and active community. I'm not sure why I'd want to change.

Neovim seems like a fun project ("let's reimplement vim!") but it feels a bit redundant, like a reimplementation for the sake of doing a reimplementation. There's an intangible reason why vim is so popular and has such a following. vim is well engineered, simple, and has been well cared for over the years. If I'm integrating something so deeply into my workflow, electing it the main way I interface with my code, it's going to be the 25 year old project that's beyond reliable, has evolved conservatively and is ubiquitous. Ten years ago I was writing code in the language du jour using vim, and ten years from now I'll be working with the hot new language. In vim.

vim isn't a broken relic of the 90's, it's one of the best, most valuable tools in my toolbox.

Re: Vim 8.0 released

#210

Earlier quoted context omitted.

I tried that. Evil seems to mess up on things now and then. Clicking the mouse acts as a command or something, wiping out ".". And macros, now and then, act up. As in, they won't record properly or something. On large Rust files, things grind to a halt if I run a macro on every line, whereas in Vim proper, things always stay speedy. In concept though, it is the best solution. Maybe I just have a broken config or some…

> And macros, now and then, act up. As in, they won't record properly or something. What you may be experiencing is an erroneous action stopping the macro. For example, if you press h at the beginning of the line, macro recording would be stopped. To make this behaviour less annoying add: (setq evil-kbd-macro-suppress-motion-error t) . Sublime-like multi-cursors in emacs are sometimes more useful than macros. I use a…

Hot damn that was probably it. Thanks!
Post reply on HN