From: Junio C Hamano <gitster@pobox.com>
To: Marc Branchaud <marcnarc@xiplink.com>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
Jeff King <peff@peff.net>,
Yaakov Smith <Yaakov.Smith@wisetechglobal.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: General output formatting
Date: Thu, 27 Feb 2025 10:40:19 -0800 [thread overview]
Message-ID: <xmqqfrjz6xkc.fsf@gitster.g> (raw)
In-Reply-To: <18ed50b3-e5a4-43b3-a543-f9a3d2c309e6@xiplink.com> (Marc Branchaud's message of "Thu, 27 Feb 2025 12:14:42 -0500")
Marc Branchaud <marcnarc@xiplink.com> writes:
> I have no opinion on exactly how to "butcher" the output for a
> terminal. I guess it depends on how well Git wants to support
> copy/paste of its output.
Yup, that is a fine balancing act. Given the current behaviour,
$ cat .git/config
[core]
somevalue = "true\b\b\b\bfalse"
$ git config --local --list
core.somevalue=false
supporting copy-paste may not be such a good thing to do, though ;-)
next prev parent reply other threads:[~2025-02-27 18:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 23:44 \b character escapes in CLI usage Yaakov Smith
2025-02-26 7:38 ` Jeff King
2025-02-26 8:09 ` Jeff King
2025-02-26 16:02 ` Junio C Hamano
2025-02-26 16:38 ` Kyle Lippincott
2025-02-26 22:06 ` Jeff King
2025-02-26 15:59 ` Junio C Hamano
2025-02-26 23:36 ` brian m. carlson
2025-02-26 23:55 ` Junio C Hamano
2025-02-27 0:03 ` Junio C Hamano
2025-02-27 14:06 ` General output formatting (was: Re: \b character escapes in CLI usage) Marc Branchaud
2025-02-27 17:06 ` General output formatting Junio C Hamano
2025-02-27 17:14 ` Marc Branchaud
2025-02-27 18:40 ` Junio C Hamano [this message]
2025-02-27 16:26 ` \b character escapes in CLI usage Phillip Wood
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=xmqqfrjz6xkc.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Yaakov.Smith@wisetechglobal.com \
--cc=git@vger.kernel.org \
--cc=marcnarc@xiplink.com \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
/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