summaryrefslogtreecommitdiff
path: root/Documentation/RelNotes/1.7.11.5.txt
diff options
context:
space:
mode:
authorLibravatar Martin Ågren <martin.agren@gmail.com>2017-08-02 21:40:51 +0200
committerLibravatar Junio C Hamano <gitster@pobox.com>2017-08-03 11:08:10 -0700
commit033fe3d92ca16c36fb45ed7cb58d42344088e7bd (patch)
treed6fc688e298b0574b957ece266ef82431368698e /Documentation/RelNotes/1.7.11.5.txt
parentgit.c: let builtins opt for handling `pager.foo` themselves (diff)
downloadtgif-033fe3d92ca16c36fb45ed7cb58d42344088e7bd.tar.xz
git.c: provide setup_auto_pager()
The previous patch introduced a way for builtins to declare that they will take responsibility for handling the `pager.foo`-config item. (See the commit message of that patch for why that could be useful.) Provide setup_auto_pager(), which builtins can call in order to handle `pager.<cmd>`, including possibly starting the pager. Make this function don't do anything if a pager has already been started, as indicated by use_pager or pager_in_use(). Whenever this function is called from a builtin, git.c will already have called commit_pager_choice(). Since commit_pager_choice() treats the special value -1 as "punt" or "not yet decided", it is not a problem that we might end up calling commit_pager_choice() once in git.c and once (or more) in the builtin. Make the new function use -1 in the same way and document it as "punt". Don't add any users of setup_auto_pager just yet, one will follow in a later patch. Suggested-by: Jeff King <peff@peff.net> Signed-off-by: Martin Ågren <martin.agren@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/RelNotes/1.7.11.5.txt')
0 files changed, 0 insertions, 0 deletions