From: The Grey Wolf <greywolf@starwolf.com>
To: git@vger.kernel.org
Subject: ANSI sequences produced on non-ANSI terminal
Date: Wed, 22 Sep 2021 22:21:22 -0700 (PDT) [thread overview]
Message-ID: <20210923052122.2F655CE@eddie.starwolf.com> (raw)
Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.
What did you do before the bug happened? (Steps to reproduce your issue)
Logged on to a hard terminal and ran 'git status .' and
'git pull'.
What did you expect to happen? (Expected behavior)
I expected that colour sequences would not be output, or at least
not hardcoded to ANSI standard. In the case of 'pull', I expected
that the stats would be just printed using <string>\r.
What happened instead? (Actual behavior)
I got escape sequences that made the output unreadable.
What's different between what you expected and what actually happened?
One produces mangled ouptut and the other doesn't.
Anything else you want to add:
I searched google and the documentation as best I was able for
this, but I am unable to find anywhere that will let me disable
(or enable) colour for a particular term type. Sometimes I'm on
an xterm, for which this is GREAT. Sometimes I'm on a Wyse WY60,
for which this is sub-optimal. My workaround is to disable colour
completely, which is reluctantly acceptable, but it would be nice
to say "If I'm on an xterm/aterm/urxvt/ansi terminal, enable
colour or cursor-positioning, otherwise shut it off." If this
seems too much of a one-off to handle, fine, but most things that
talk fancy to screens are kind enough to allow an opt-out based on
terminal type. :)
Please review the rest of the bug report below.
You can delete any lines you don't wish to share.
[System Info]
git version:
git version 2.32.0
cpu: amd64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
uname: NetBSD 9.99.88 NetBSD 9.99.88 (EDDIE) #16: Tue Aug 31 19:14:47 PDT 2021 greywolf@eddie.starwolf.com:/sys/arch/amd64/compile/EDDIE amd64
compiler info: gnuc: 10.3
libc info: no libc information available (actually there's a LOT of it,
but I'm not sure you really want it -- please let me know if you do).
$SHELL (typically, interactive shell): /bin/bash
$TERM: wy60
[Enabled Hooks]
I don't know enough about git yet to use these.
next reply other threads:[~2021-09-23 5:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 5:21 The Grey Wolf [this message]
2021-09-23 21:20 ` ANSI sequences produced on non-ANSI terminal Jeff King
2021-09-23 21:54 ` Junio C Hamano
2021-09-23 22:04 ` Randall S. Becker
2021-09-25 6:45 ` Kevin Daudt
2021-09-24 0:58 ` [PATCH] config: add an includeIf.env{Exists,Bool,Is,Match} Ævar Arnfjörð Bjarmason
2021-09-24 21:07 ` Jeff King
2021-09-24 21:28 ` Junio C Hamano
2021-09-24 21:59 ` Jeff King
2021-09-27 16:30 ` Junio C Hamano
2021-09-27 20:15 ` Jeff King
2021-09-27 20:53 ` Randall S. Becker
2021-09-27 21:37 ` Jeff King
2021-09-27 21:56 ` Randall S. Becker
2021-09-27 23:52 ` Ævar Arnfjörð Bjarmason
2021-09-28 0:41 ` Jeff King
2021-09-28 2:42 ` Ævar Arnfjörð Bjarmason
2021-09-28 5:42 ` Jeff King
2021-09-28 19:28 ` Ævar Arnfjörð Bjarmason
2021-09-28 0:24 ` Junio C Hamano
2021-09-24 23:57 ` ANSI sequences produced on non-ANSI terminal Greywolf
2021-09-25 5:49 ` Jeff King
2021-10-01 23:17 ` Greywolf
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=20210923052122.2F655CE@eddie.starwolf.com \
--to=greywolf@starwolf.com \
--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).