ENTER key ignored right after new tab opened

Open
#3,157 2 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
zsh

Research direction

Reproduce the issue by adding sleep 10 to .zshrc, opening a new tab, and typing a command before startup completes. Trace the new-tab shell startup and keyboard input handling; done means ENTER executes the typed command and moves to a new line during startup.

Written by the indexing model from the issue text.

Description

area:window-tabs-panes bug needs-info ready-to-implement triaged
Discord username (optional)

No response

Describe the bug

When opening a new tab, I'll get for around half a second the message "Starting zsh...".
While this message appears, keyboard inputs will still be recognized - except the ENTER key.

I've set up an alias cs=cd /path/to/some/dir to a directory that I switch right often to. So my personal workflow often includes that I open a new tab, type "cs" and press ENTER to immediately switch to that directory.

In iterm and other terminals, this works flawlessly. In Warp though, it will just show "cs" because the ENTER key is ignored. I have to press ENTER again after a short while.

To reproduce
  • Add "sleep 10" to .zshrc -> this makes it easier to reproduce because starting ZSH will take longer
  • Open new tab
  • Press immediately some letters and press ENTER
  • Wait until 10 seconds have passed
  • See that ENTER has been ignored
Expected behavior

Command is executed, cursor is in new line.

Screenshots

No response

Operating system

MacOS

Operating system and version

13.4

Shell Version

zsh 5.9 (x86_64-apple-darwin22.0)

Current Warp version

v0.2023.05.23.08.05.stable_00

Regression

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

Recent working Warp date

No response

Additional context

I'm using Oh my zsh which could slow down the proces

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.