From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: Jeff King <peff@peff.net>,
Yaakov Smith <Yaakov.Smith@wisetechglobal.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: \b character escapes in CLI usage
Date: Wed, 26 Feb 2025 15:55:09 -0800 [thread overview]
Message-ID: <xmqqtt8g9s82.fsf@gitster.g> (raw)
In-Reply-To: <Z7-lbGnlzGbhrHZN@tapette.crustytoothpaste.net> (brian m. carlson's message of "Wed, 26 Feb 2025 23:36:12 +0000")
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
> We already have precedent for this in core.quotePath and could easily
> use similar logic here. That format, while using octal, which I find
> ugly and hard to read, does have the pleasant side effect that it works
> correctly with POSIX printf(1) (which I'm sure was intentional), unlike
> hex escapes.
It was intended to be "the normal C quoting":
https://lore.kernel.org/git/87ek6s0w34.fsf@penguin.cs.ucla.edu/
next prev parent reply other threads:[~2025-02-26 23:55 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 [this message]
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
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=xmqqtt8g9s82.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Yaakov.Smith@wisetechglobal.com \
--cc=git@vger.kernel.org \
--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 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.