You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it would be fantastic if the tool could support as many sub-sections as one would desire. For example, your main section might be matched by ^commit. You want to see the overall commit as you scroll. However, you also want to see if this was ^(added:|removed:|renamed:|Δ) as you scroll, too.
You can kind of emulate the desired behavior with this command:
It keeps the commit header sticky, and you can see ^(added:|removed:|renamed:|Δ) is also sticky -- except the commit sha does not update! It just keeps the first three lines fixed (as expected, of course).
It would be awesome to have subsections that can stack separately, similar to what we can almost emulate.
I think this would also be nice to even make '•' as sub-sub section, this way you can sticky see the file that has changed, too!
I think it would be fantastic if the tool could support as many sub-sections as one would desire. For example, your main section might be matched by
^commit
. You want to see the overall commit as you scroll. However, you also want to see if this was^(added:|removed:|renamed:|Δ)
as you scroll, too.You can kind of emulate the desired behavior with this command:
It keeps the
commit
header sticky, and you can see^(added:|removed:|renamed:|Δ)
is also sticky -- except the commit sha does not update! It just keeps the first three lines fixed (as expected, of course).It would be awesome to have subsections that can stack separately, similar to what we can almost emulate.
I think this would also be nice to even make
'•'
as sub-sub section, this way you can sticky see the file that has changed, too!How this might look in practice:
The text was updated successfully, but these errors were encountered: