How to jump to the next file header when viewing a multi-file diff through less? #1868
-
I'm not sure if this is possible, but it would be nice to jump between file headers in less. Maybe there is some search magic that would work here? I used |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Hi @voidus, you've seen the navigate feature, right?
So what you're aiming for is to use those settings to cause it to visit precisely the boundaries you want. Let me know what you come up with. I think that that particular requirement (file boundaries, but not within-file commit hunk boundaries) is one that's less obvious how to achieve. I believe that for this reason I personally sometimes set the diff context to a high number (e.g. |
Beta Was this translation helpful? Give feedback.
-
No I didn't, that's why I wrote this. Thank you!
…On Fri, 27 Sept 2024, 10:18 Dan Davison, ***@***.***> wrote:
Hi @voidus <https://github.com/voidus>, you've seen the navigate
<https://dandavison.github.io/delta/navigation-keybindings-for-large-diffs.html>
feature, right?
--navigate
Activate diff navigation.
Use n to jump forwards and N to jump backwards. To change the file labels used see
--file-added-label, --file-copied-label, --file-modified-label, --file-removed-label,
--file-renamed-label.
--navigate-regex <REGEX>
Regular expression defining navigation stop points
So what you're aiming for is to use those settings to cause it to visit
precisely the boundaries you want. Let me know what you come up with. I
think that that particular requirement (file boundaries, but not
within-file commit hunk boundaries) is one that's less obvious how to
achieve. I believe that I personally sometimes set the diff context to a
high number (e.g. -U999) so that there are no within-file hunks.
—
Reply to this email directly, view it on GitHub
<#1868 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA6LCXUAQTXAFTEOJAGLWLZYUIFTAVCNFSM6AAAAABO6CYCMOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANZXGI2DKOA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
Hi @voidus, you've seen the navigate feature, right?
So what you're aiming for is to use those settings to cause it to visit precisely the boundaries you want. Let me know what you come up with. I think that that particular requirement (file boundaries, but not within-file commit hunk boundaries) is one that's less obvious how…