Replies: 4 comments
-
This is actually the case for all the unimpaired( |
Beta Was this translation helpful? Give feedback.
-
First time contributor here! Please find my first attempt above. I'm curious, will this require a "wrapped around document" status for the editor? This is how search behaves, but not how diagnostic's next/previous behaves. Also, wrapping a document with search seems optional, whereas this optionality is not found with diagnostic gotos, is this intended behaviour? The way I have written the node captures for the first/last elements also seems less than elegant, and I would be keen to hear any advice on a different approach of finding these nodes. I'm eager to handle this solution, however I may require guidance due to my inexperience in open-source contributing. |
Beta Was this translation helpful? Give feedback.
-
Yeah I think we prefer the current behavior where it doesn't wrap. You can use |
Beta Was this translation helpful? Give feedback.
-
Maybe this could be configurable as well? For example with a general |
Beta Was this translation helpful? Give feedback.
-
Summary
By default, other goto style commands wrap around the file when they reach the end. This is not happending with go to next change, and it just stays on the last one when you reach it.
Reproduction Steps
In a file in a git repo create a couple change. Then cycle through them with ']g'
Helix log
No response
Platform
maxOS ssh'ed into Linux
Terminal Emulator
iTerm
Helix Version
23.05
Beta Was this translation helpful? Give feedback.
All reactions