-
-
Notifications
You must be signed in to change notification settings - Fork 958
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
hints --type=linenum --linenum-action does no path path to editor #4675
Comments
That will be because whatever nvr is, is discarding the second argument. |
Hi @kovidgoyal Thank you very much for your fast replay. As stated in the bug report, manually invoking the linenum-action works fine. It seems that kitty is not providing the {path} to the linenum-action. |
Works for me with:
kitty -o 'map ctrl+shift+o kitten hints --type=linenum --linenum-action=window vim --remote +{line} {path}'
|
Does not repro for me with
or with
|
Hi, I bumped into this while after updating my system. {path} seems to be incorrect only if the string matched has a slash and line and column in the following format:
I used this map to test with
this prints with the above path as input (however it highlights the path and both numbers) while In a previous version it used to also work as expected with (FYI: it would be nice to also have a {column} :) e.g. gcc/clang also provide the column number in the above format) |
This issue can be reproduced in the master branch. |
Hi @kovidgoyal, tyvm for fixing this issue! |
Describe the bug
Opening a file in neovim via hints mode opens the base path to the file correctly but passes only the +{line} option and ignores the path.
kitty.conf
text acted on [1]
text acted on [2]
path opened in neovim
Manually invoking the linenum-action works fine.
To Reproduce
Steps to reproduce the behavior:
Environment details
The text was updated successfully, but these errors were encountered: