Thread (30 messages) flat view 30 messages, 5 authors, 2016-06-15

Re: [PATCH 0/4] git --paginate: do not commit pager choice too early

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:49:08

Possibly related (same subject, not in this thread)

Junio C Hamano [off-list ref] writes:
Jonathan Nieder [off-list ref] writes:
quoted
Patch is against master.  There is a small semantic conflict with
jn/grep-open: SIMPLEPAGER should be changed to SIMPLEPAGERTTY in the
prerequisites for the test_default_pager function.  Please let me
know if I should push a merge commit to help resolve that.
Thanks for advance warning; please double check the merge result in 'pu'
when I push it out...
I hate an enumeration that pretends to be exhausitive but is not.

    So delay the pager startup when possible:
    
    1. run_argv() already commits pager choice inside run_builtin() if a
       command is found.  For commands that use RUN_SETUP, waiting until
       then fixes the problem described above: once git knows where to
       look, it happily respects the core.pager setting.

... and for commands that do not use RUN_SETUP, what happens?

    2. list_common_cmds_help() prints out 29 lines and exits....
    3. help_unknown_cmd() prints out a few lines to stderr.  It is not
       important to paginate this, so don’t.

Missing from the above enumeration are are external commands.  They depend
on commit_pager_choice() to be called before execv_dashed_external() gets
called.  For example, "git -p request-pull $args" no longer works with
this patch.

Sigh..
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help