Leap: Neovim’s Answer to the Mouse

Re:Leap: Neovim’s Answer to the Mouse by dotancohen on Saturday October 08, 2022 @03:10PM (#33135052)

As a two decade VIM user, this idea looks like "VIM for people who still think like mice". The mouse lets one jump to an arbitrary location on the current window. But the real goal is to jump to a specific object, be it a method signature, or variable declaration, or the beginning of the file, or the end of the line, etc, or the next occurrence of a keyword, or the beginning of this if clause, etc. VIM already has provision for getting to these places, and once they are in muscle memory you won't need to break your train of thought to use them.

Don't use VIM like you used Notepad. Use VIM like you use a manual transmission.

[ Parent | on HN ]

Re:Leap: Neovim’s Answer to the Mouse by latifk on Saturday October 08, 2022 @03:35PM (#33135293)

Built in targets should be preferred, sure, but there are plenty of situations not covered by those targets.

In that case it’s quite handy to have a motion plugin at your disposal. Or otherwise use plugins that extend the built in targets (like targets.vim)

[ Parent | on HN ]

Re:Leap: Neovim’s Answer to the Mouse by nickysielicki on Saturday October 08, 2022 @08:09PM (#33137211)

It’s the vim user that is stuck thinking like a mouse/notepad user, because the vim user has an index into the file that needs to be moved (your cursor), whereas the avy user doesn’t have to think about where he’s coming from, it’s all relative to the viewport. The typical emacs user navigates through project-wide greps and jumps, buffer local searches, and things like avy.

[ Parent | on HN ]