I really tried to like it, but a long time ago I got used to, I think, easymotion. I wasn't able to shake the habit and now I use hop.nvim. I guess I'm too set in my ways 😄
flash works how I want it to. I don’t want to type a specific number of letters. I just want to look at where I want to go, press a letter and then the red letter and boom I’m there. Leap’s need for 2 letter minimum jars me, especially around symbols.
Been using it for a while and it keeps improving my workflow(no more 13j etc). I would love to get used to the remote operations but somehow the mental overhead is too big and i spend more time thinking bout the commands than it would take me to do it regularly. Do you experience similar issues with plugins you would like to use more but dont?
@@ghostsssssss4884 I definitely experience this with different plugins. If you don't use the plugin at all then could be an indicator of having too many but sometimes your workflow just changes over time.
I've been using flash for a couple of months now. flash.nvim resolved my search workflows, but your video covers a feature I do not know exists, it's really helpful!
I use to like those but then I felt they messed with my vanilla way of doing things with additional overhead. I'm currently loving the precognition plugin that actually helps you use vanilla mappings by adding jump hints in virtual text.
None actually, all cause a context change. You screen changes, you then have to type a random character or maybe two. Instead just longpress j, k to go the correct line number and b,w or f to get to where you want. Decrease key repeat time to make this faster. This doesn't cause a brain context change and you can focus on your code instead of random flashing characters.
Yeah. Also / works pretty fine most of the times. And if it doesn't, i just manually navigate. But yeah, i hate having to think about what i do (except when i do macros, which in fact i do only if i want to have some fun, or have big changes to make and a good macro is worth it)
Also: i tend to use the defaults as much as possible. This for 3 reasons: - i am lazy - defaults are mantained by neovim devs, so they will always work (unlike plugin stuff which may break, get deprecated or who knows what) - using defaults means that if i fuck up and need to run neovim without plugins, or on a different computer, then my muscle memory will still be valid
At 3:00 you mention that flash giving one keybind to jump in any window is key to you. If anyone is wondering how to do that in leap, you can use require('leap').leap({target_windows = {winid1, winid2}}) to target as many windows as you'd like. Combine this with require('leap.util').get_enterable_windows() which gives all visible windows except the current one, and vim.api.nvim_get_current_win() and you can jump to anything on the screen with one keybind
I think both of these plugins offer an illusion of efficiency. Yes you may save few keystrokes, but you need to think more about how and where do you want to move? Should you use vim motions or the plugin? And while you are using the plugin, you aren't perfecting vim motions. How hard is it to write say 12j + whatever horizontal jump? Or search for something then just press n free times to skip to the one you want?
I think this is a really fair question. Some folks want to get better at default vim bindings and others want to customize and use different plugins. I do think there is some potential efficiency gains with using either of these plugins but you need to learn and develop the muscle memory for that efficiency. One of the best features of Neovim is that everyone can choose what they prefer and customize the editor. This decision is also not set in stone, I have seen a couple comments of people who said they relied on these plugins too much and went back to using built in vim motions. Whichever you choose, have fun and continue learning!
no flash is objectively better when you want to clickly move to a specific word in the current window view especially when there are multiple of those words. this is a very specific use case, yes, but it does happen to me a lot. moving x amount of lines and dragging the cursor to that spot can feel tedious after using flash
Honestly I love this extension, and that exactly why I stopped using it. I used it almost exclusively, for every movement, and it came to a point that I didn't know some native vim movement s. I had to stop using it in order to learn them.
You mention that you would leave leap for flash just for the bi-directional ability to jump places, it leaps offers that as well. Like you, I want a single keybind to jump in any direction. You can also make that jump to any window as well if you’d like.
I remember back when I suggested you should use Flash, glad to see this video now :D You have been missed on Twitch land, hope to see you there one day.
Thanks for suggesting it! I finally got around to trying it out. Hopefully I can get back into Twitch again, maybe once I can get my kids to bed earlier 😂
@@joebu7538 what function or command are you using to jump? My initial thought is you keep typing characters to narrow it down but let me know if you have a specific example.
@@ascourter If I require("flash").jump() + "e", I can see an overflow of matches to "e" highlighted compared to jump labels--covering only ~26 of them. I want to move the jump labels to the next/previous set of 26 like in leap with and . Is there something like that in flash?
Haha I think you could if that's what you'd like. You'd have to set a mark somewhere before you were able to jump there is a problem for me. Let me know if you use marks to jump around and how you use them.
