Dracula Theme issue in Vim

Open
#3,917 1 comment 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

The issue names no source file, test, or entry point. First reproduce the cursor-color problem in a JSON file in Vim on Warp v0.2023.11.14.08.02.stable_02, then trace the terminal theme or rendering path. Done means the cursor remains visually distinct from pink JSON text, as shown by the expected behavior.

Written by the indexing model from the issue text.

Description

area:shell-terminal area:ui-framework bug ready-to-implement triaged
Discord username (optional)

No response

Describe the bug

The cursor has the same color as the text below it when you open a JSON file in Vim, making the text invisible.

To reproduce

Open a JSON file in Vim and move the cursor over to a pink text.

Expected behavior
image
Screenshots
image
Operating system

MacOS

Operating system and version

14.0 (23A344)

Shell Version

zsh 5.9 (x86_64-apple-darwin23.0)

Current Warp version

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