[BUG] Artifacts in Kitty terminal

[ujjwal3067]

Describe the bug

• Doesn't seems to be working on kitty terminal

• To Reproduce

• Just simply Hello Dialog example from readme.md

Expected behavior

• I expected tui to not have artifacts

Screenshots

Environment

• MacOs
• Backend used: ncurses (the default one)
• Current locale (run locale in a terminal)

  LANG="en_CA.UTF-8"
  LC_COLLATE="en_CA.UTF-8"
  LC_CTYPE="en_CA.UTF-8"
  LC_MESSAGES="en_CA.UTF-8"
  LC_MONETARY="en_CA.UTF-8"
  LC_NUMERIC="en_CA.UTF-8"
  LC_TIME="en_CA.UTF-8"
  LC_ALL=

• Cursive version (from crates.io, from git, ...)
  • from crates.io

[gyscos]

Hi, and thanks for the report!

On my machine (Linux with en_GB.UTF-8 locale), the example renders fine in the kitty terminal. We may need more investigation to understand the issue.

Is the selected locale actually available? (Is it listed if you run locale -a?) Does the issue happen with all other examples (from the examples/ directory) as well? If you try another backend (like crossterm), is the issue still present? Did you try another terminal emulator? Is the issue only happening on kitty?

[Yevgnen]

Got the same issue on macOS 12.6. The issue happens for all the examples. Also happened when backend changed to crossterm. The issue does not exist in iTerm2 and the default Terminal.app. locale outputs

LANG="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_CTYPE="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_ALL="en_US.UTF-8"

and it is in locale -a.

[sschuldenzucker]

Anyone ready for some necromancy? I do get these same errors with the default backend (ncurses) but not with the crossterm backend.