Skip to content
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

Show file defining a mapping for Telescope keymaps #1771

Open
MarcelRobitaille opened this issue Mar 4, 2022 · 5 comments
Open

Show file defining a mapping for Telescope keymaps #1771

MarcelRobitaille opened this issue Mar 4, 2022 · 5 comments
Labels
enhancement Enhancement to performance, inner workings or existent features

Comments

@MarcelRobitaille
Copy link

Is your feature request related to a problem? Please describe.
It would be great if Telescope keymaps could show the file defining a particular keymap. Right now, I am having the problem that something (presumably one of my plugins) is defining a keymap that is interfering with one of my custom keymaps. The name of this mapping is not similar to the names or functionality of any of my plugins, so I have no clue where it comes from.

Describe the solution you'd like
Telescope keymaps shows a third column showing the file name and line number of each mapping.

I looked through internal.keymaps, which pointed me to vim.api.nvim_get_keymap and help maparg, which does not seem to provide this information. So I'm not sure how easy/possible this would be.

@MarcelRobitaille MarcelRobitaille added the enhancement Enhancement to performance, inner workings or existent features label Mar 4, 2022
@MarcelRobitaille
Copy link
Author

Turns out I can just do verbose map <mapping>. Still would be a nice feature though in my opinion.

@cosmicbuffalo
Copy link

I also think this would be nice to have

@rwijtvliet
Copy link

Me too!

@MikeLemo1
Copy link

Any progress on that since?

@jamestrew
Copy link
Contributor

I think it's unlikely this will happen without some api to get this info that's better than calling verbose map on each keymapping and parsing out the definition path.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Enhancement to performance, inner workings or existent features
Projects
None yet
Development

No branches or pull requests

5 participants