git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: ANSI sequences produced on non-ANSI terminal

From
GGreywolf <greywolf@starwolf.com>
Date
Sep 24, 2021, 23:57 UTC
Message-ID
<592a799b-0d16-1615-4737-3c634d029d7f@starwolf.com>
In-Reply-To
<YUzvhLUmvsdF5w+r@coredump.intra.peff.net>
Greetings and thank you ALL for your responses!
On 9/23/2021 14:20, Jeff King wrote:
> Git doesn't have any kind of list of terminals, beyond knowing that "dumb"
> should disable auto-color. It's possible we could expand that if there are
> known terminals that don't understand ANSI colors. I'm a bit wary of having
> a laundry list of obscure terminals, though.

Oh, gods, I wouldn't have that at all! No, I just want it NOT to spit out not only the colour codes, but the cursor positioning codes as it seems wont to do when I do a fetch. I'm more than happy to turn coloring off (conditional on TERM would be a bonus, however it's done) on my own; in fact, I have done so, but the fetch/pull still seem to be messing up my screen, with color turned off (unless I'm not turning it off *enough*, which is entirely possible).

> If we built against ncurses or some other terminfo-aware library we could
> outsource that, but that would be a new dependency. I'm hesitant to do that
> even as an optional dependency given the bang-for-the-buck (and certainly
> making it require would be right out).

Well understood. Also, not asking for people to jump thru flaming hoops. Just trying to figure out how to get git to stop assuming things. (as stated, I am aware it could be my fault for not setting variables properly all the way).

Show 8 quoted lines
> Obviously you can wrap Git with a script to tweak the config based on the
> current setting of the $TERM variable. It would be nice if you could have
> conditional config for that. E.g., something like:
> 
> [includeIf "env:TERM==xterm"] path = gitconfig-color
> 
> That doesn't exist, but would fit in reasonably well with our other 
> conditional config options.
That is a consideration; and one I had not thought of.
> As far as generating non-ANSI codes, that's all Git knows how to do.

Just need to have it NOT generate ANSI codes, if requested. I'm certainly not requesting the world of terminals to be incorporated -- just some universal readability.

As far as the suggestion to use "screen", I'm not going to be starting up a screen session every time I log in. :)

				Thank you all very much!
				--*greywolf;
Previous: Junio C HamanoNext: Jeff King
Message 21 of 23 in “ANSI sequences produced on non-ANSI terminal”
  1. The Grey WolfSep 23, 2021
  2. Jeff KingSep 23, 2021
  3. Junio C HamanoSep 23, 2021
  4. Randall S. BeckerSep 23, 2021
  5. Kevin DaudtSep 25, 2021
  6. config: add an includeIf.env{Exists,Bool,Is,Match}Ævar Arnfjörð Bjarmason, Sep 24, 2021
  7. Jeff KingSep 24, 2021
  8. Junio C HamanoSep 24, 2021
  9. Jeff KingSep 24, 2021
  10. Junio C HamanoSep 27, 2021
  11. Jeff KingSep 27, 2021
  12. Randall S. BeckerSep 27, 2021
  13. Jeff KingSep 27, 2021
  14. Randall S. BeckerSep 27, 2021
  15. Ævar Arnfjörð BjarmasonSep 27, 2021
  16. Jeff KingSep 28, 2021
  17. Ævar Arnfjörð BjarmasonSep 28, 2021
  18. Jeff KingSep 28, 2021
  19. Ævar Arnfjörð BjarmasonSep 28, 2021
  20. Junio C HamanoSep 28, 2021
  21. GreywolfSep 24, 2021
  22. Jeff KingSep 25, 2021
  23. GreywolfOct 1, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.