git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dragan Simic <dsimic@manjaro.org>
To: git@vger.kernel.org
Subject: [RFC] New configuration option "diff.statNameWidth"
Date: Sat, 02 Sep 2023 20:03:11 +0200	[thread overview]
Message-ID: <eb8f524eca3975f086715ec32a8a1fbb@manjaro.org> (raw)

Hello,

I'd like to implement support for a new configuration option named 
"diff.statNameWidth" and submit the patch, so I'd like to check first 
would that patch be accepted and merged.

Similarly to the already existing configuration option 
"diff.statGraphWidth",[1][2] "diff.statNameWidth" as a new configuration 
option would limit the width of the filename part in generated diffstat 
outputs, just like the command-line option "--stat-name-width=<n>" 
already does.

Having "diff.statNameWidth" as a new configuration option would be quite 
usable, and it would fit together nicely with the already existing 
"diff.statGraphWidth" configuration option.  For exaple, I have quite a 
few aliases in my ~/.gitconfig that contain "--stat-name-width=<n>", and 
having this new configuration option would allow those aliases to be 
much shorter.  Of course, it would benefit all other uses in which 
diffstats are generated.

Please advise.

Links:
[1] 
https://git-scm.com/docs/git-diff#Documentation/git-diff.txt---statltwidthgtltname-widthgtltcountgt
[2] 
https://git-scm.com/docs/git-config#Documentation/git-config.txt-diffstatGraphWidth

             reply	other threads:[~2023-09-02 18:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-02 18:03 Dragan Simic [this message]
2023-09-02 18:47 ` [RFC] New configuration option "diff.statNameWidth" Junio C Hamano
2023-09-02 18:56   ` Dragan Simic
2023-09-02 22:16     ` Junio C Hamano
2023-09-03  3:43       ` Dragan Simic
2023-09-11 18:56         ` Dragan Simic
2023-09-11 23:02           ` Junio C Hamano
2023-09-12  0:26             ` Dragan Simic

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=eb8f524eca3975f086715ec32a8a1fbb@manjaro.org \
    --to=dsimic@manjaro.org \
    --cc=git@vger.kernel.org \
    /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).