warpdotdev / warpdotdev/warp

Shell stops responding with tmux is executed with default

Open
#4,216 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Discord username (optional)

kunalsin9h

Describe the bug

Os: Arch Linux
Installed: .pkg.tar.zst

I have a small code in my .zshrc with run tmux all the time by default, like when i open new terminal tmux will also be initialized, and i will be in tmux.

This is causing warp to stop working (only shell) buttons are working but no keyboard interaction is happening.

When i remove the code what run tmux everything works and manually running tmux also works.

To reproduce
  1. Use bellow code to automatically start tmux on every new zsh session.
if command -v tmux &> /dev/null && [ -n "$PS1" ] && [[ ! "$TERM" =~ screen ]] && [[ ! "$TERM" =~ tmux ]] && [ -z "$TMUX" ]; then
  exec tmux
fi
  1. Open warp
Expected behavior

No response

Screenshots

No response

Operating system

Linux

Operating system and version

Arch Linux

Shell Version

zsh 5.9

Current Warp version

Newest warp for linux v0.2024.02.20.08.02.stable_01-1-x86_64

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?

No

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

Start with the .zshrc reproduction using zsh 5.9 on Arch Linux, then compare an automatically executed tmux session with one started manually in Warp. Trace the shell keyboard-input path and verify that keyboard interaction works while tmux is initialized automatically, without affecting the working buttons.

Written by the indexing model from the issue text.

Assessment

Tech stack
arch-linux, shell, zsh
Domain
cli, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.