You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently learned about a pair of motions that Vim added in patch 7.3.610 (gn and gN) which reference the last used search pattern. This allows you do do things like "dgn" to delete the next match, or cgn to change the next match. If used on their own, they visually select the next match.
Since many of these types of things can technically be done with ":s", they may not be strictly necessary, but it does seem like it could make some of my editing patterns more efficient.
The text was updated successfully, but these errors were encountered:
academician
changed the title
Feature request: gn/GN motions
Feature request: gn/gN motions
Sep 19, 2014
I will try and get that added to a future version. Looks pretty straight forward, mostly just need to get a newer build of gVim so i can play around with the feature
This was harder than I thought it would be, mainly because gn has different semantics in each of its three different flavors: as a motion, as a normal command, and as a visual command. Nevertheless, the infrastructure of VsVim does all the heavy lifting and we just have to coordinate the various actors.
One of the things I like about working on VsVim is getting exposed to these kind of features in vivid detail, like, reference manual level detail. I'm pretty sure gn is going to "get into my fingers" because it really hits the spot for repeating those two part edit actions that look end with n.n.n.n. but can now all be .....
I recently learned about a pair of motions that Vim added in patch 7.3.610 (gn and gN) which reference the last used search pattern. This allows you do do things like "dgn" to delete the next match, or cgn to change the next match. If used on their own, they visually select the next match.
Since many of these types of things can technically be done with ":s", they may not be strictly necessary, but it does seem like it could make some of my editing patterns more efficient.
The text was updated successfully, but these errors were encountered: