Raphael 'kena' Poss
Raphael 'kena' Poss
> The most lightweight variant I have seen is based on nanotime() per scheduler ticks, as my colleague @knz prototyped here (the code just counts ticks, but imagine adding up...
In case it wasn't clear from the latest comments from @tbg and myself: we believe that doing things at the granularity of goroutines is too fine grained, and raises painful...
thank you for your interest! We're still evaluating whether this approach is useful in practice. Once we have a good story to tell, we'll share it with the go team.
Note: this issue is compounded (and can be made worse) by https://github.com/charmbracelet/lipgloss/issues/108
NB: I could imagine the map from string to tea.Key being defined in the bubbletea package directly. If you prefer that, let me know.
> I think that makes sense and is probably nicer next to the other tea.Key code. Ok see https://github.com/charmbracelet/bubbletea/pull/491 Then to merge this PR I'll need a release number for...
Could we make this wrap the output instead of truncating it?
cc @muesli @meowgorithm
@chabad360 can you say more? What are the symptoms?
Thanks. I think you are experiencing the symptoms of a different problem, but i believe it could also improve with this change https://github.com/charmbracelet/bubbletea/pull/569