random output of ANSI escape sequences with 0.7.1 about lipgloss

[Jcambass]

@aymanbagabas I upgraded my example to v0.8.0 and it indeed seems to fix the issue.

[muesli]

This is lipgloss querying the terminal for its color support. It should only ever happen once on startup, and you're obviously not supposed to see it. How do you reproduce that?

[hopefulTex]

Was this a problem with version > 6.0, or just 7.1?
Do you have a repo with at least your View?
Does this happen on a fresh Kitty install?

[benleb]

sorry for the delay, easter time 🐰

uargh sorry, I did not mean "reproducible" 😅🤦‍♀️ I just can see if it works or not quite fast (no hour-long wait times to see if a fix works for example). I unfortunately don't know which function call triggers this.

This is lipgloss querying the terminal for its color support.

ah nice thanks! which commands trigger this "color support check"?

Was this a problem with version > 6.0, or just 7.1?

also with 0.7.0

Do you have a repo with at least your View?

hm do you have a bubbletea app in mind? it is not yet on that level unfortunately 😅 Just plain lipgloss. The code is currently not in a public repo, but I work on that (hours or days). But do not expect a proper structured go project or something like this... It's a tool that was/is hacked together by me and other people with very less go experience and no time 😅

Does this happen on a fresh Kitty install?

Hm I did not test it explicitly, but I use kitty exclusively for this tool and just adjusted the font and font size in the config, everything else is default.

[benleb]

code available here: https://github.com/benleb/gloomberg

[muesli]

@benleb Can you point me to the place in code where you print/render to stdout? Is it possible that this is happening concurrently with another print call?

[benleb]

hey, thanks & sorry 🙄 your hint with the concurrent print calls may have pointed me in the right direction! That was indeed the case but after fixing it I found out it had nothing todo with the issue 😅 but lead me to something else and I might found the file causing the issue.... Gimme some more hours to test and narrow it down, I will get back to you with more details then 👍

[benleb]

hey! sorry, I am a little late. I did a lot of testing and I think I got the faulty line 🕵️‍♂️

It seems that the border I set here is the problem. I will let it run for now and give a final confirmation tomorrow, but I am pretty confident right now :D

I used it to create some lines between these boxes here (like the pink ones I draw here :D)

The border was used on the single items of the "lists". The items then JoinVerticaled and die "lists" then JoinHorizontaled. The full file is here if you are interested https://gist.github.com/benleb/8677601b56dd95331ea6ee8e8b6c1715 (sorry, I can't publish the repo currently)

Thanks for your help already! And btw. also for your other tools like duf 👏

[Jcambass]

👋🏻 I've been running into what I believe is the same issue. I had troubled integrating the help component with the filepicker component.

I was quite puzzled because the help component does noop in the Update method. Yet calling the View function made the whole app freeze.

After some digging I did notice that whenever I did call the View function of the help component, quite a lot of random tea.KeyMsg where received.

Downgrading to lipgloss v0.6.0 fixed this issue.

I created a minimum reproducible example: https://gist.github.com/Jcambass/a26808e90e31e2f39a20665b49e54241

You can run this and observe the following behaviour:

• (sometimes) you are greeted with a Bummer. No Files Found. message.
• At some points after that you will see your directory listing.
• Trying to navigate your dir with the arrow keys doesn't work.
• Let the program run and open the debug.log where you see all the tea.Msg received by the main program. You should see a bunch of unexpected inputs.

[lemoony]

I can affirm the findings of @Jcambass. I have to downgrade to lipgloss v0.6.0 for now - along with bubbles which depend on v0.7.1.

[aymanbagabas]

Could you try out the new release and see if the issue still exists? https://github.com/charmbracelet/lipgloss/releases/tag/v0.8.0