[Bug/Support]: Elpaca's initial draw override first line with Kitty

[wroyca]

Confirmation

• I have checked the documentation (README, Wiki, docstrings, etc)
• I am checking these without reading them.
• I have searched previous issues to see if my question is a duplicate.

Elpaca Version

Elpaca 7a68b7d grafted, HEAD -> master, origin/master, origin/HEAD
installer:      0.1
emacs-version:  GNU Emacs 30.0 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.43, cairo version 1.18.2)
 of 2025-03-08
git --version:  git version 2.48.1

Operating System

Linux fedora 6.13.5-200.fc41.x86_64

Description

When running Emacs in terminal mode with Kitty, Elpaca's initial draw seems to override the first line. This happens when package operations such as cloning or byte-compilation are in progress. Calling (elpaca-wait) usually resolves it.

Observation show that ^[[K is mishandled (which may or may not be related). Note that I couldn't reproduce this issue with a different terminal, so it might be a bug with Kitty itself, but the following test script show that it work as intended:

echo -ne "\033[s"
echo -ne "This is a full line of text that should be partially erased."
echo -ne "\033[20G"
echo -ne "\033[K"
echo -ne "\033[u"

# Result: This is a full line of text

Steps to Reproduce

1. Using Kitty, open Emacs in terminal mode (emacs -nw).
2. Ensure Elpaca is set up to install or update packages automatically.
3. Observe the first line when package operations are in progress.
4. Notice that the first line is overwritten instead of preserving the expected content.

---

kitty --version
kitty 0.39.1 created by Kovid Goyal

[progfolio]

Thank you for the thorough bug report.
I haven't been able to reproduce this on my end yet.
I'll take a deeper look into it when have time.

[wroyca]

Thank you for the thorough bug report. I haven't been able to reproduce this on my end yet. I'll take a deeper look into it when have time.

Thank! Let me know if you need more information.

In the meantime, here are some more things I've ruled out:

• The font used didn't make a difference (tested with ligatures, without ligatures, and different fonts).
• Kitty configuration didn't make a difference (tested with my config and the default config).
• Terminal width didn't make a difference (tested with 3840×2160 (16:9) at 200% scaling).