[GH-ISSUE #495] ANSI bright not respected when a color follows #359

New issue

Closed

opened 2026-03-04 01:04:18 +03:00 by kerem · 2 comments

kerem commented

2026-03-04 01:04:18 +03:00

Owner

Originally created by @tculp on GitHub (Sep 3, 2020).
Original GitHub issue: https://github.com/rivo/tview/issues/495

echo -e "\033[01;31mhi" Produces bright/bold red text, but echo -e "\033[01;31mhi" | go run ansi.go does not show bright red text, just regular red text.

This is using the code provided on the ANSI wiki page: https://github.com/rivo/tview/wiki/ANSI.

Interestingly, faint text shows up as expected: echo -e "\033[02;31mhi" | go run ansi.go

Originally created by @tculp on GitHub (Sep 3, 2020). Original GitHub issue: https://github.com/rivo/tview/issues/495 `echo -e "\033[01;31mhi"` Produces bright/bold red text, but `echo -e "\033[01;31mhi" | go run ansi.go` does not show bright red text, just regular red text. This is using the code provided on the ANSI wiki page: https://github.com/rivo/tview/wiki/ANSI. Interestingly, faint text shows up as expected: `echo -e "\033[02;31mhi" | go run ansi.go`

kerem closed this issue

2026-03-04 01:04:19 +03:00

kerem commented

2026-03-04 01:04:19 +03:00

Author

Owner

@rivo commented on GitHub (Oct 18, 2020):

I can't reproduce this. Maybe this is because I'm using the new tcell version, to which tview was just upgraded. Or you're on a different terminal that's handling colours differently in different contexts. This is what it looks like for me (macOS, iTerm2):

vs.

Can you still reproduce your issue with the latest version? If so, please let me know your configuration (OS / which terminal).

@rivo commented on GitHub (Oct 18, 2020): I can't reproduce this. Maybe this is because I'm using the new `tcell` version, to which `tview` was just upgraded. Or you're on a different terminal that's handling colours differently in different contexts. This is what it looks like for me (macOS, iTerm2): ![image](https://user-images.githubusercontent.com/480930/96367966-32f6f280-1151-11eb-84d9-738dbdc4a54d.png) vs. ![image](https://user-images.githubusercontent.com/480930/96367973-3db18780-1151-11eb-9a72-6290b0a307f4.png) Can you still reproduce your issue with the latest version? If so, please let me know your configuration (OS / which terminal).

kerem commented

2026-03-04 01:04:19 +03:00

Author

Owner

@rivo commented on GitHub (Nov 17, 2020):

Since there was no further information provided, I'm closing this issue. If you still require information, please open a new issue and reference this one.

@rivo commented on GitHub (Nov 17, 2020): Since there was no further information provided, I'm closing this issue. If you still require information, please open a new issue and reference this one.