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.
I use Spacemacs for Elixir programming and honestly, Emacs is slow, I would often type commands and then wait for it to complete. I think some reboot like Neovim did for Vim, could be beneficial as it is awesome editor, but it is just too slow to start and slow to use. It might be that Spacemacs layer is adding additional complexity, and maybe going through Helm is the issue, I don't know, just it does take quite a b…
Vim 8.0 released
171–180 of 308 posts
Re: Vim 8.0 released
#172I moved to nvi. Feels good to go back a notch and realise that you actually don't need all of the other stuff to produce quality code.
Me, I just wrote my own editor that works exactly the way that I want it to work. Every Jedi needs to build their own light saber, and come on, it's just 6KLOC or so.
I've never even considered what goes into making an editor.
Re: Vim 8.0 released
#173I 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 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…
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 and like https://github.com/gabesoft/evil-mc .
Regarding other points:
- yes, for huuuge files I still use vim
- Occasional bugs due happen, as in every editor running custom plugins. In emacs debugging and editing plugins code is natural. You can use emacs to debug itself and reload parts of code without restarting.Re: Vim 8.0 released
#174I didn't see anything in the release notes but does anyone know if Vim 8 adds true colour terminal support? (I realise that NeoVim has this.)
Re: Vim 8.0 released
#175Earlier quoted context omitted.
you know what? I'm prepared to cut Bram Moolenaar a lot of slack given the goodness he gave us for 20 years through 7 versions of one of my top 3 pieces of useful software.
he's a great guy but at some point it's time to move on
Maybe you want to move on just for the sake of moving on? To a new generation? Can you explain why? Seems to me that the person who knows the code base 200%, who wrote/vetted the entire codebase, is better placed to add features, than newbie refactorers who didn't?
Re: Vim 8.0 released
#176Oh Vim... If you're going to lightweight and vi-like, than do that. If you're going to go the Emacs route (and if you're adding async, packaging, and lambdas, make no mistake, you're starting in the steps to building an inferior Emacs), than get a half-decent extension language. Or just up and die. We don't need a Vi clone that does the Emacs thing, we've got Evil/Spacemacs for that.
The thing is, having tried Evil/Spacemacs, they're still really Emacs not Vim. At some point you have drop out of the pseudo Vim world do things the Emacs way, keybindings and all. For me personally, that's not what I want. e.g. I like to use C-h as an alternative to backspace, it helps relieves my RSA not have to reach for backspace. Spacemacs provides that binding in some places but not all. To get get C-h to consi…
I guess what I really want is for Vim to decide what it wants to be. You can be simple, or you can be extensible. Vim is kind of trying to be both. Traditionally, Emacs did extensible, and Vi did simple. It's fine if Vim wants to go the emacs route, it's just that I'd rather it stopped doing it so badly: At this point, Vim's extensibility story is embarrassing. It's 2016, the built-in language is rubbish, the external language interfaces are second-class at best. This has to change if Vim really wants to go in that direction. And if doesn't, why bother pretending?
Re: Vim 8.0 released
#177Oh Vim... If you're going to lightweight and vi-like, than do that. If you're going to go the Emacs route (and if you're adding async, packaging, and lambdas, make no mistake, you're starting in the steps to building an inferior Emacs), than get a half-decent extension language. Or just up and die. We don't need a Vi clone that does the Emacs thing, we've got Evil/Spacemacs for that.
The thing is, having tried Evil/Spacemacs, they're still really Emacs not Vim. At some point you have drop out of the pseudo Vim world do things the Emacs way, keybindings and all. For me personally, that's not what I want. e.g. I like to use C-h as an alternative to backspace, it helps relieves my RSA not have to reach for backspace. Spacemacs provides that binding in some places but not all. To get get C-h to consi…
or many packages there are many "vim-optimized" packages nowadays, e.g. evil-ediff, evil-org or evil-magit.
> e.g. I like to use C-h as an alternative to backspace, it helps relieves my RSA not have to reach for backspace.
I would do such remapping on the system level. E.g. I personally have my layout implemented in C++ on system level: https://github.com/kozikow/keyremaplinux
> I found loads of other things like that where I just want it to work the Vim way.
In Emacs in general it's easier to customise to do things your way. After a bit investment into learning elisp you can make it work however you want, including vim way. vim is not as customisable.
Re: Vim 8.0 released
#178Re: Vim 8.0 released
#179Earlier quoted context omitted.
I haven't used nvi in several years (mostly because, unlike nvi, vim has become universally available on the systems I use), but it's not minimalist. nvi has a number of features that the original vi does not. Perl integration and infinite undo are two examples.
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.
Re: Vim 8.0 released
#180Earlier quoted context omitted.
Could you mention which plugins you switched to? Is there a list somewhere that details the alternatives that work better in neovim?
Off the top of my head: - vim-plug for a plugin manager (very good regardless of concurrency) - neomake for building - vim-go added async job support using neovim a while ago for most of its functionality, which I use for writing Go My full inventory is here: https://github.com/shazow/dotfiles/blob/master/.vim/plugins....