Replies: 9 comments
-
i'm gonna take a stab at this one |
Beta Was this translation helpful? Give feedback.
-
I look forward to seeing what you come up with! I don't know any Rust but I'd love to see how this looks, then maybe I can contribute one day :) |
Beta Was this translation helpful? Give feedback.
-
brace yourself.... Kazam_screencast_00000.mp4 |
Beta Was this translation helpful? Give feedback.
-
the pull request is very much in draft status. it needs to be cleaned up. after more trial and error and failing than i'd like to admit, it finally worked, so i pushed what i had. i'll get it cleaned up, and then get feedback. |
Beta Was this translation helpful? Give feedback.
-
Great work! |
Beta Was this translation helpful? Give feedback.
-
cleaned up the merge request search works in both directions |
Beta Was this translation helpful? Give feedback.
-
i think this issue might be dead. seems that this feature is provided in a separate PR: #4650 @ocharles - maybe pull #4650 and verify that it satisfies this issue? fwiw my work is here: #4708 |
Beta Was this translation helpful? Give feedback.
-
@wes-adams I don't think #4650 is a satisfactory fix for me. I use three-way conflict markers, and ]g doesn't seem to take me to each individual section, whereas your PR does. I'll try and put an asciinema together, but I don't think it's that #4650 does anything wrong, it's just doing something different. |
Beta Was this translation helpful? Give feedback.
-
@ocharles that is already covered by searching with |
Beta Was this translation helpful? Give feedback.
-
vim-unimpaired
adds]n
and[n
to navigate SCM conflict markers. It'd be great to have this navigation feature in Helix, too!Beta Was this translation helpful? Give feedback.
All reactions