Repository navigation
Add pager functionality back in - #155
matthiasbeyer wants to merge 1 commit into
Conversation
Use $GIT_PAGER or core.pager or $PAGER to bring back paging behaviour. Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
CI fails because of code I did not touch. |
| .num_args(1), | ||
| ) | ||
| .arg( | ||
| Arg::new("no-pager") |
There was a problem hiding this comment.
Do you happen to know if there is a NO_PAGER or other env var equivalent to the fairly standardized NO_COLOR that can disable this universally in a shell?
There was a problem hiding this comment.
I think the more common thing people do is PAGER=cat in front of the command (or GIT_PAGER=cat of course). I cannot remember that I saw NO_PAGER ever... 🤔
There was a problem hiding this comment.
Yes I've certainly used the cat stand in a time or two myself. I just looked around and it seems like you're right and there isn't a widely recognized env var far this. SYSTEMD_PAGER and MANPAGER are worth having in a back pocked along with GIT_PAGER, but nothing I see is generic and should be implemented here. So carry on!
2 participants
Use $GIT_PAGER or core.pager or $PAGER to bring back paging behaviour.
As discussed in #121 - this brings back the paging behaviour, but not the internal self-written pager functionality, but
$GIT_PAGERorcore.pageror$PAGERinstead.What do you think?