git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Thomas Koutcher via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Thomas Koutcher <thomas.koutcher@online.fr>
Subject: [PATCH 0/2] diff- family --stat width
Date: Thu, 21 Apr 2022 20:15:57 +0000	[thread overview]
Message-ID: <pull.1256.git.git.1650572159.gitgitgadget@gmail.com> (raw)

diff- family commands do not use the full terminal width. This is visible in
Tig which uses git diff-files to show diffs for unstaged changes. When
trying to display diffs with long filenames, the diffstat does not improve
when the Tig window size is increased.

This patch makes diff-files, diff-index and diff-tree --stat behave like
diff --stat and use the full terminal width. The handling of the config
option diff.statGraphWidth is also added.

Thomas Koutcher (2):
  diff- family --stat: use the full terminal width
  diff- family --stat: honour config option to limit graph width

 builtin/diff-files.c | 2 ++
 builtin/diff-index.c | 2 ++
 builtin/diff-tree.c  | 2 ++
 diff.c               | 9 +++++----
 4 files changed, 11 insertions(+), 4 deletions(-)


base-commit: 6cd33dceed60949e2dbc32e3f0f5e67c4c882e1e
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1256%2Fkoutcher%2Fdiff-family-stat-width-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1256/koutcher/diff-family-stat-width-v1
Pull-Request: https://github.com/git/git/pull/1256
-- 
gitgitgadget

             reply	other threads:[~2022-04-21 20:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-21 20:15 Thomas Koutcher via GitGitGadget [this message]
2022-04-21 20:15 ` [PATCH 1/2] diff- family --stat: use the full terminal width Thomas Koutcher via GitGitGadget
2022-04-21 20:15 ` [PATCH 2/2] diff- family --stat: honour config option to limit graph width Thomas Koutcher via GitGitGadget
2022-04-21 21:33 ` [PATCH 0/2] diff- family --stat width Junio C Hamano
2022-04-29 17:22   ` Thomas Koutcher

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=pull.1256.git.git.1650572159.gitgitgadget@gmail.com \
    --to=gitgitgadget@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=thomas.koutcher@online.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).