leap.nvim VS nvim-treehopper

Also I really like leap.nvim which in my opinion is the best thought out "hop" variation.

Your plugins are great but I haven't tried mini.jump2d. However, compared to hop.nvim I prefer leap.nvim's jumping philosophy because it uses information you already have before starting the jump, and you just have to type one "virtual" character, which in my opinion is a smoother experience.

Here's the repo if you haven't heard about it: https://github.com/ggandor/leap.nvim Otherwise, does anyone know if there are ways to emulate that behavior with existing keybings? And, if all else fails, would you like to see it as a feature request?

leap.nvim absolutely turned my movements and navigation experience in neovim upside down.

I like Leap

Nice, but you've reinvented the wheel :) https://github.com/goldfeld/vim-seek -> https://github.com/justinmk/vim-sneak -> https://github.com/ggandor/leap.nvim

I use it as my mapping for leap.nvim (https://github.com/ggandor/leap.nvim), but I only map for normal and help buffers, since mapping it in every buffer type messes up things like quickfix lists and file trees.

Take a look at nvim-treehopper (https://github.com/mfussenegger/nvim-treehopper), a tree-sitter based plugin that lets you select regions of code

This copies the idea of nvim-treehopper. Just a work in progress hack (pretty usable though), but planning to make a full-fledged plugin, if someone else won't do it :) (Needless to say, my gists can be considered unlicensed, do whatever you want with them.)

I also suggest taking a look at this one : mfussenegger/nvim-treehopper

https://github.com/mfussenegger/nvim-ts-hint-textobject does what you are proposing.