From: Junio C Hamano <gitster@pobox.com>
To: K Jayatheerth <jayatheerthkulkarni2005@gmail.com>
Cc: git@vger.kernel.org, jltobler@gmail.com, lucasseikioshiro@gmail.com
Subject: Re: [GSoC Patch 0/2] add unicode support to git repo structure
Date: Fri, 21 Aug 2026 09:59:17 -0700 [thread overview]
Message-ID: <xmqqse47pfyy.fsf@gitster.g> (raw)
In-Reply-To: <20260821135410.429698-1-jayatheerthkulkarni2005@gmail.com> (K. Jayatheerth's message of "Fri, 21 Aug 2026 19:23:43 +0530")
K Jayatheerth <jayatheerthkulkarni2005@gmail.com> writes:
> Currently, `git repo structure` always renders its table output using plain
> ASCII characters (`|`, `-`, `*`), regardless of the user's locale. This
> series introduces Unicode box-drawing characters (`│`, `├`, `─`, `┼`, `┤`)
> and bullet points (`•`) when a UTF-8 locale is detected, providing a cleaner
> and more visually distinct hierarchical output on modern terminals while
> gracefully falling back to the existing ASCII formatting otherwise.
Generally speaking, Unicode box-drawing characters do not work as
ASCII art components as well as they should, because terminals often
do not agree on how wide they should be rendered.
So I am not very enthusiastic about this change.
next prev parent reply other threads:[~2026-08-21 16:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 13:53 [GSoC Patch 0/2] add unicode support to git repo structure K Jayatheerth
2026-08-21 13:53 ` [GSoC Patch 1/2] gettext: fall back to env-derived charset when unset K Jayatheerth
2026-08-21 13:53 ` [GSoC Patch 2/2] repo: add Unicode support for `repo structure` output K Jayatheerth
2026-08-21 16:59 ` Junio C Hamano [this message]
2026-08-23 13:19 ` [GSoC Patch 0/2] add unicode support to git repo structure Oswald Buddenhagen
2026-08-23 15:01 ` Junio C Hamano
2026-08-23 17:06 ` Tuomas Ahola
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=xmqqse47pfyy.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jayatheerthkulkarni2005@gmail.com \
--cc=jltobler@gmail.com \
--cc=lucasseikioshiro@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.