reset command (zsh on Mac) doesn't reset

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
macos, zsh

Research direction

The report names no repository files or tests. Start by reproducing reset in Warp on macOS with zsh and compare it with another terminal; done means the view and local command history reset without closing or reopening the app.

Written by the indexing model from the issue text.

Description

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

No response

Describe the bug

I have an alias like:

HISTORY_FILES=(
  "$HISTFILE"
  "$HOME/.${ZSH_OR_BASH}_sessions" # Mac default
  "${LESSHISTFILE:-.lesshist}"
)

alias clear-history='history -p'
alias reset-history='clear-history && rm -rf "${HISTORY_FILES[@]}" && reset'

It neither resets the view nor the local command history. Closing and opening the window resets the view but not the local command history. Currently must quit the app to take effect.

To reproduce

Just reset.

Expected behavior

No response

Screenshots

No response

Operating system

MacOS

Operating system and version

14.3.1 (23D60)

Shell Version

zsh 5.9 (x86_64-apple-darwin23.0)

Current Warp version

v0.2024.02.06.08.02.stable_01

Regression

Yes, this bug started recently or with an X Warp version

Recent working Warp date

No response

Additional context

I believe it worked recently but can't confirm.

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

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.