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
Tab doesn't cycle between sets after update #356
Comments
Currently, you can only use Enter and Shift+Enter to cycle through the individual results. I believe this Tab and Shift+Tab scrolling functionality was removed to simplify refactoring and pressing tab was intentionally disabled in #353. Previously, as you mentioned, this calculated the middle of the next/previous set of matches and centered them on the screen. If you rely on this functionality, you can roll back to |
Thank you, perhaps the README should be updated until this functionality is back. |
Yep, sorry I forgot to remind you that this feature was missing. It's still possible to use Page Up/Down or use other IJ/GO scrolling actions if that works for you, but of course the original functionality of jumping past areas with no tags was more convenient than normal IJ/GO scrolling. |
Additional to this "Enter" and "Shift+Enter" do not work too |
This regression should be fixed in the next update, |
This should now be available in AceJump |
Installed 3.8.5 and still get "File is read-only" upon pressing Tab. UPD: This only happens when your cursor is inside text into which a language was injected (for example, an SQL query inside a JS file). Moving the cursor out of the portion with injected language makes cycling with Tab work and will show results inside the injected portion as well. Uninjecting the language also makes Tab cycling work when the cursor is inside the previously injected text. |
After updating to 3.7, pressing
Tab
no longer cycles between sets, instead "File is read-only" is displayed. Tested on a fresh install of GoLand 2020.3.4 with default settings and bundled plugins only.To Reproduce
Ctrl+;
.Tab
key.Expected behavior
The next set of results is displayed.
Desktop:
The text was updated successfully, but these errors were encountered: