When ssh to FreeBSD 12.4 vi deleted lines do not disappear on screen.

Open
#3,660 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
macos, zsh

Research direction

No source file or test is named. Reproduce the issue by SSHing to a FreeBSD 12.4 host, opening a file with vi, and pressing dd; compare Warp with other terminals, and consider the issue done when the deleted line disappears immediately and the following line moves up.

Written by the indexing model from the issue text.

Description

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

No response

Describe the bug

When I use vi on FreebSD 12.4 and want to delete a line with double d, the lines stays visible on the screen, it is deleted when saved. The cursor goes a line down after the double d command.

To reproduce
  1. ssh to a FreeBSD12.4 host
  2. open a file with vi
  3. double d command on a line
Expected behavior

The line should disappear on the screen as the double d command is given and the line below should move up.

Screenshots

No response

Operating system

MacOS

Operating system and version

13.5.2 (22G91)

Shell Version

zsh 5.9 (x86_64-apple-darwin21.3.0)

Current Warp version

v0.2023.09.06.18.09.stable_00

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: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.