CLI run in "alternate screen" mode glitches on subsequent renders

Open
#2,597 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
macos, rust, zsh
Domain
cli

Research direction

Start by reproducing klog today --follow test.klg in Warp on macOS and compare its alternate-screen rendering with Terminal.app, Hyper, and htop. Investigate the terminal rendering and cursor-update path; done means follow-mode output stays at the top and the cursor no longer jumps or blinks during updates.

Written by the indexing model from the issue text.

Description

bug needs-info ready-to-implement triaged
Discord username (optional)

No response

Describe the bug

The time tracking tool klog has a --follow mode which makes it fill the whole terminal estate and dynamically update the output.

It doesn't render as expected in Warp. It's rendered at the wrong position and the cursor glitches/jumps on updates.

To Reproduce
  1. Install klog: brew install jotaen/klog/klog
  2. Create a new klog file: touch test.klg
  3. To reproduce, run: klog today --follow test.klg
Expected behaviour
  1. I expect the output to be rendered at the top of the terminal, which it correctly does in other terminals like Terminal.app and Hyper. Other tools, like htop, which fills the whole terminal behaves correctly, in Warp too.
  2. I expect the cursor to not jump/blink on updates/re-renders.
Screenshots

https://user-images.githubusercontent.com/516549/216321822-a9f674a9-9812-4f5e-956f-906d1f36849f.mov

Operating System

MacOS

OS Version

13.1

Shell Version

Zsh: 5.8

Warp Version

v0.2023.01.24.08.03.stable_01

Additional context

No response

Does this block you from using Warp daily?

No

Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e

None

Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from warpdotdev/warp

All issues in warpdotdev/warp

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.