gum input - missing cursor when running in container images (since v0.10.0)

[ThomasBuchinger]

Describe the bug
I am writing a script that uses gum input --value "default-value". The default value must be edited by the user.

The problem is, that there is no cursor on screen, making it hard to know where the cursor is exactly. The cursor still exists and it can be moved by pressing the arrow keys and counting the number of characters, but there is no on screen indication for the current cursor position

• The bug only exists when running inside a container image (tested on ubuntu:22.04 and charmcli/gum:v0.10.0)
• Running gum v0.10.0 without a container works
• Using the older charmcli/gum:v0.9.0 image works
• The bug seems to still exists on main-branch. Tested with docker.io/golang image and go install github.com/charmbracelet/gum@main

To Reproduce

# Produces the bug
podman run -it --rm  docker.io/charmcli/gum:v0.10.0 input

# Produces the bug
podman run -it --rm docker.io/golang
go install github.com/charmbracelet/gum@main
gum input

# v0.9.0 image works
podman run -it --rm  docker.io/charmcli/gum:v0.9.0 input

# The native binary works
$ ./gum --version
gum version v0.10.0 (0f0f8e9)
$ ./gum input                     

Expected behavior
There should be a blinking box, showing the current position of the cursor

Desktop (please complete the following information):

• Fedora37, podman 4.5.0
• RHEL 8.4, podman 4.4.3

Additional context
I don't really have access to a different Linux distro or container runtime at the moment. If there are any additional setting I can try, let me know

[xabru]

It looks like you're trying to run gum in a non-interactive environment.

[caarlos0]

yes, the -i in podman run should have set it interactive... seems like it didn't? is this still happening?

[caarlos0]

fwiw, could repro this with main on docker as well:

[caarlos0]

I think its because it reports TERM as xterm, which isn't pick up as supporting colors by termenv.

For now you can workaround by setting COLORTERM, CLICOLOR_FORCE, or changing TERM to something else (like xterm-256color)

cc/ @aymanbagabas do you know if this works the same way in lipgloss v2?

[aymanbagabas]

cc/ @aymanbagabas do you know if this works the same way in lipgloss v2?

Good point! It would produce the same results in v2. This is related to colorprofile. TERM=xterm should return a ANSI color profile

[aymanbagabas]

@caarlos0 I've opened charmbracelet/colorprofile#22 to resolve this issue in v2

[caarlos0]

thanks @aymanbagabas!

[caarlos0]

see muesli/termenv#174

[caarlos0]

fixed on main