Git development
 help / color / mirror / Atom feed
From: "Wang Bing-hua" <louiswpf@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>,  "shejialuo" <shejialuo@gmail.com>
Cc: <git@vger.kernel.org>
Subject: Re: [PATCH] remote: align --verbose output with spaces
Date: Wed, 18 Dec 2024 05:49:14 +0000	[thread overview]
Message-ID: <18122f6da7729ff9.8ab23eb43f7bb6f4.c74125d7d6163423@host> (raw)
In-Reply-To: <xmqqr066ysa6.fsf@gitster.g>



On 17/12/2024 12:21, Junio C Hamano wrote:
>> On Tue, Dec 17, 2024 at 12:39:36PM +0000, Wang Bing-hua via GitGitGadget wrote:
>>> From: Wang Bing-hua <louiswpf@gmail.com>
>>> 
>>> Remote names exceeding a tab width could cause misalignment.
> 
> If all of them are named with ten ASCII characters, on a terminal
> with fixed-width font, things will still display aligned ;-)

Indeed :)
I did consider this scenario and wrote "could". I should have worded
this more clearly.

> With a Devil's advocate hat on, a change like this will completely
> break tools when they are reading the "--verbose" output and
> expecting that the fields are separated with a TAB (in other words,
> the tab is *not* about alignment in the first place for them).
> 
> Now with that hat off.
> 
> For users with that many remotes where the alignment of URLs in the
> interactive "git remote -v" output matter, I am not sure if this
> change is a real improvement enough that it is worth the possible
> risk of breaking existing tools.  With that many remotes defined,
> wouldn't they be doing "git remote -v" piped to "grep '^name<TAB>'"
> or something?  That use case would break with the change, too.

Agreed on all points. Another point to consider is to align with
"git branch -v" since it also uses spaces for alignment.
This patch was also originally lifted from "builtin/branch.c".


  reply	other threads:[~2024-12-18  5:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-17 12:39 [PATCH] remote: align --verbose output with spaces Wang Bing-hua via GitGitGadget
2024-12-17 13:23 ` shejialuo
2024-12-17 15:24   ` Wang Bing-hua
2024-12-17 20:21   ` Junio C Hamano
2024-12-18  5:49     ` Wang Bing-hua [this message]
2024-12-18 13:52     ` shejialuo
2024-12-18 14:09       ` Wang Bing-hua
2024-12-17 17:18 ` [PATCH v2] " Wang Bing-hua via GitGitGadget
2024-12-17 20:47   ` Junio C Hamano
2024-12-18  8:37     ` Wang Bing-hua
2024-12-18 15:39       ` Junio C Hamano
2024-12-19  2:14         ` Wang Bing-hua

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=18122f6da7729ff9.8ab23eb43f7bb6f4.c74125d7d6163423@host \
    --to=louiswpf@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=shejialuo@gmail.com \
    /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