Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Remove Ex-Mode from Neovim

github.com

Post reply on HN
Print view View original

111–120 of 123 posts

Re: Remove Ex-Mode from Neovim

#111

Post by chongli »

goldfeld wrote: post #74
thegeomaster wrote: post #67

Earlier quoted context omitted.

I'm interested to hear why you're using evil-mode instead of vim if that's how you feel. I'm using vim with slimv for Lisp hacking at the moment and I have to admit that there are some whoopsies, but not enough to make me learn to use a whole new editor :)

Well, rant and occasional surprise aside, I've found evil-mode to truly be a better implementation of vi than vim itself, at least where it concerns me (as formerly a pretty advanced vim user and plugin developer, it took me some adapting to stop using all the ex vim idioms and the like.) It's faster to handle big files and execute macros, overall snappier and has a profoundly better %s///g with real time preview. I…

I tried using evil and it just messed up my brain too much. I learned emacs and vim properly and their methods of operation are now ingrained in my muscle memory, entirely separate from one another. To go back now would be like asking someone to use a mouse and keyboard to drive their car.

Re: Remove Ex-Mode from Neovim

#112

Post by forwardslash »

Expez wrote: post #25
untothebreach wrote: post #4

Earlier quoted context omitted.

Yea, I finally got fed up one day and put nnoremap Q in my .vimrc. No more "how did I get HERE?"

I usually record my throwaway macros to q (because hitting qq is so easy), so I've bound Q to 'call the most recently defined macro'. I would post something to put in your .vimrc, but I use the vim emulator evil-mode in Emacs. This way, I can skip the awkward @q step, and keep hitting Q instead of @@ to re-run the macro.

How do you call the most recently defined macro? I just have Q bound to @q, but if I could make it more general that would be awesome.

Re: Remove Ex-Mode from Neovim

#114

Post by davis »

forwardslash wrote: post #112
Expez wrote: post #25

Earlier quoted context omitted.

I usually record my throwaway macros to q (because hitting qq is so easy), so I've bound Q to 'call the most recently defined macro'. I would post something to put in your .vimrc, but I use the vim emulator evil-mode in Emacs. This way, I can skip the awkward @q step, and keep hitting Q instead of @@ to re-run the macro.

How do you call the most recently defined macro? I just have Q bound to @q, but if I could make it more general that would be awesome.

@@ re-runs the last macro.

Re: Remove Ex-Mode from Neovim

#115

Post by davis »

mcantor wrote: post #91

Hadn't heard of nvim until today. Can anyone sell me on this project? I looked at the homepage and README, but they're both pretty hand-wavey. What problems does nvim solve for experienced vim users?

It is trying to refactor Vim and update it. If those sources are all too "hand-wavey", here's the consolidated feed for the development in the last months: http://neovim.org/news/archive/

Re: Remove Ex-Mode from Neovim

#116

Post by randy909 »

weaksauce wrote: post #96
burke wrote: post #71

Earlier quoted context omitted.

I use for this. It's very gratifying, mashing the spacebar to repeat a macro.

using space for the leader is one thing that I absolutely love... I was using , for it but space is so much easier and nicer to use. you are not limited to one finger to start the leader command so it makes both sides of the keyboard nice to use for leader chords. it only took about a week to retrain myself for it. here's the command... put it at the top of your vimrc before anything else so it works with your plugin…

See space.vim for another cool use for the spacebar. https://github.com/spiiph/vim-space

Re: Remove Ex-Mode from Neovim

#117

Post by pydave »

nXqd wrote: post #83
gfodor wrote: post #68

Earlier quoted context omitted.

More like IE3. Nobody uses ex mode.

It's not true. Some still uses it extensively in the case of editing the last commands. But there is alternative way. I am happy that they will remove this mode in the future :)

q:

That gives you a buffer you can look through previous commands and use normal-mode commands to edit them.

Also, you don't need Ex mode to edit last commands. You can just press Up from cmdline.

Re: Remove Ex-Mode from Neovim

#118

Post by pydave »

4ad wrote: post #58

Ugh. Some awful distributions remove ed(1) by default, when that happens, I use vi's ex mode as a substitute. Now these people want to remove that too, amazing. I can only hope this vim fork never becomes the default vi on any systems I am forced to use...

Nah, they're keeping that:

https://github.com/neovim/neovim/issues/1089#issuecomment-56...

You just can't switch between ex and vi modes.

Re: Remove Ex-Mode from Neovim

#119

Post by pydave »

Slackwise wrote: post #61
unclebunkers wrote: post #44

Earlier quoted context omitted.

You want to change the name from neovim because they want to remove functionality that I'm guessing maybe 1% of the users use regularly. Even though for 99%, neovim is vim only modernized and cleaned up. It's illogical as you're doing a disservice to the users, and neovim is a clear name that describes what it is. New vim.

- It is a fork of Vim. - It is omitting some features. - It is adding a number of high level features. - It will not be fully backwards compatible. Prefixing 'new' to the name of the forked project is as lazy as it can get [1]. 'Neo' is one step from that. Vim itself wouldn't be a good name if it was just meaning "Vi iMproved", but 'Vim' is also a dictionary word meaning "energy; enthusiasm". A positive dictionary wo…

Vigor already exists as a cruel parody of vi: https://en.wikipedia.org/wiki/Vigor_(software)

But I like your idea. Something like Vittle as a whittled-down version of vim.

Re: Remove Ex-Mode from Neovim

#120

Post by BruceIV »

untothebreach wrote: post #4
octo_t wrote: post #3

Earlier quoted context omitted.

aka "Oh, that's the key I have been hitting by accident"

Yea, I finally got fed up one day and put nnoremap Q in my .vimrc. No more "how did I get HERE?"

This is wonderful, I must do this, I keep hitting `q` instead of `:q` when I want to quit Vim, and it's a pain to get out of...
Post reply on HN