-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make f iterate through search results if pressed immediatly after use #41
Comments
Hmmm. It should be possible, but might be a few weeks before I get to it. |
Thanks! |
I'm starting to want this feature too :) Since you are familiar with clever-f, does it have a way to repeat the search after doing other things? Or repeat only works immediately after invoking |
Thanks for your response and help! As I understand it, cleverf only works immediately post f, and it doesn't work with . to repeat on either vanilla . or with tpope repeat. I would see this working in its simplest form as:
At a deeper level though, I wonder if we are close to a more elegant combination of single key f and Sneak which combines short and medium motion jumps intuitively and flexibly. Potential Option - Iterative combination of F and Sneak
Then:
Then:
OR:
Then:
Else:
The plusses of this would be:
This should mean that I can get anywhere +/- a few lines with just a few keystrokes (<5?) AND have to use only one key instead of F/f/S/s. Not sure if this second idea is fully baked, but I think it would have great flexibility. Other than the trouble of coding it, which might be huge and would be more than I can handle to be sure, I can't see a downside to just hitting esc if I realize that one letter got me where I wanted), and love the idea of doing this all with one key, plus not needing ;. Again, thanks so much for your help. Moving medium distances in Vim is something I do a thousand times a day in Vim, so trying to make that nicer is a real gift. |
As always, if you have mapped to something other than s/S, it will work as intended.
FYI, this is mostly implemented, possibly broken, in https://github.com/justinmk/vim-sneak/tree/experiment-clever_s Not that you should waste your time trying out that branch, but just to update you. I think I like the feature, thanks for suggesting it! It works with counts too, so But it is failing a few tests and I need to update the documentation and tie up some other things. Regarding your second idea:
I wouldn't be opposed to this except it kind of breaks streak-mode, because it potentially moves the window (if the first character has an off-screen match), which changes the potential targets. Even if you don't use streak-mode, I think it might be too "spammy", because it will match much more often than two letters, which means the first character will often move the window if there is off-screen text. |
Coo, thanks! Is there an easy way to do branches with Vundle? If not I need to like actually learn GIT, which, obviously I know I am on github right now. Yeah, I see your point. I think clever-f functionality + sneak might be great. I'll play with it more and let you know what I think. Incidentally, I had 's' taken by fold/unfold so I mapped this to option S, and really like the ergonomics. |
Vundle infamously does not support "pinning" to a branch. VundleVim/Vundle.vim#35 But, the feature should be in master by next week... |
ahh, thanks! I suspected that. All the best, Brian Brian Toomeyphone: 660.243.0784 skype: toomey832 Upper Knight St On Wed, Jan 29, 2014 at 9:48 AM, justinmk notifications@github.com wrote:
|
Let me know how it goes... |
@toomey8 FYI, this feature is disabled by default now, because it is too surprising for new users. You can enable it like so:
Sorry for the inconvenience. |
Wow. This is a fantastic plugin.
One feature I would really love is the way 'f' is used to repeat immediately after a motion, a la rhysd/clever-f.vim, especially because I've remapped ; to : in normal mode to make entering commands 50% easier.
Arguments for this:
Would this be possible? Maybe crib from clever-f?
The text was updated successfully, but these errors were encountered: