Server terminal settings affect clients of wish served bubbletea apps.

[bytedancer1]

I'm running a wish app in a docker container, and noticed a number of things along the way, and one maybe bug. Interested to learn more about best practices with respect to these topics. I don't know much about the details of how terminals function, just what I've needed to make my own terminal work as an entusiastic user.

1. The TERM environment variable that wish server process is exec'd with matters. If it's xterm-256color, xterm-256color clients have a good experience. If the server's TERM environment variable is blank, xterm-256color clients have a bad experience color wise.

2. If the wish server is detached from a terminal, clients have a bad experience.

$ TERM=xterm-256color ./wishapp &

(invoking shell/terminal now closed before any client connects)

incoming clients have a bad experience.

HOWEVER,

$ TERM=xterm-256color ./wishapp &
(first client connects before invoking shell/terminal closed)
Now, the terminal can be closed and all subsequent clients have a good (color) experience.

In the end I solved the problem with docker by using run -t to provide a terminal to the wish server and everything works. But it feels like the server's terminal should not have any affect on clients. But maybe it's jsut my ignorance about terminals and how wish does it's magic.

Is this likely something I'm doing wrong or a bug? Should I open an issue or just be happy I have wish?

[caarlos0]

Hey!

Currently, you need to use this

wish/examples/bubbletea/main.go

Lines 81 to 83 in 94694ca

	renderer := bubbletea.MakeRenderer(s)
	txtStyle := renderer.NewStyle().Foreground(lipgloss.Color("10"))
	quitStyle := renderer.NewStyle().Foreground(lipgloss.Color("8"))

On v2, it'll just work:

wish/examples/bubbletea/main.go

Line 68 in ab914a8

func teaHandler(s ssh.Session) (tea.Model, []tea.ProgramOption) {