warpdotdev / warpdotdev/warp

Incorrect display when using a command giving you output in less

Open
#4,068 4 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug ready-to-implement triaged
Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

Description

Discord username (optional)

No response

Describe the bug

When I perform a command that gives its output in less I can see the whole page, but as I start scrolling up and down the top part of the screen gets hidden behind the code block of the input. I can no longer scroll up and see the top part of the output

To reproduce
  1. enter git repo
  2. run "git log"
  3. scroll down using "j"
  4. scroll up using "k"
  5. You now won't be able to see the top lines of the log
Expected behavior

I expect to be able to scroll to the top of the contents of less

Screenshots

No response

Operating system

MacOS

Operating system and version

13.6.0

Shell Version

zsh 5.9 (x86_64-apple-darwin22.0)

Current Warp version

v0.2024.01.09.08.02.stable_02

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

No response

Additional context

No response

Does this block you from using Warp daily?

Yes, this issue prevents me from using Warp daily.

Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)

Yes, this I confirmed this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None

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.

Research direction

No source file or test is named. Reproduce the issue on macOS by running git log in Warp, entering the pager, and moving with j and k; then trace the terminal output and pager rendering path. Done means the complete output remains reachable when scrolling back to the top, as it does in other terminals.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.