:Git log display is inconsistent with command-line defaults

[finite-state-machine]

The fugitive version of git log shows entries like this:

commit 3ad7eb55bb1db72125df258d3ee1afd12dca32a6
Merge: 83b3e7d 9ed4719
Author: Finite State Machine ([email protected])
Date:   Sat Mar 23 16:02:58 2024 -0400

    text: 'unused_char()' bug fix (use w/iterators was unsafe) + tests

Whereas git log usually shows entries like this:

commit 3ad7eb55bb1db72125df258d3ee1afd12dca32a6 (HEAD -> TableGeometry, origin/x32util-main, x32util-main)
Merge: 83b3e7d 9ed4719
Author: Finite State Machine ([email protected])
Date:   Sat Mar 23 16:02:58 2024 -0400

    text: 'unused_char()' bug fix (use w/iterators was unsafe) + tests

When outputting to a non-TTY, git log matches fugitive's behaviour:

commit 3ad7eb55bb1db72125df258d3ee1afd12dca32a6
Merge: 83b3e7d 9ed4719
Author: Finite State Machine ([email protected])
Date:   Sat Mar 23 16:02:58 2024 -0400

    text: 'unused_char()' bug fix (use w/iterators was unsafe) + tests

IMO, fugitive should do at least one (ideally, both) of the following:

• pass --decorate to git log by default
  • ideally, it should respect any explicit log.decorate config setting, but change log.decorate to short if none is specified vs. default auto
• allow the user to customize the default arguments to git log via a g:fugitive_... global variable.

(This is probably typical of a class of bugs where fugitive's behaviour differs from what users expect due to git's defaults changing between TTY and non-TTY stdout/stderr; in case it's helpful, I've prepared a list of all of the places where git manpages mention "terminal": man-git-mentions-terminal.txt)

Aside, my thanks to @tpope and all contributors for a wonderful tool!