Update syntax/error highlighting after `rehash`/`hash -r`

Open
#2,927 3 comments 5 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
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
bash, rust, zsh

Research direction

No files, tests, or entry points are identified in the issue. Start by locating Warp's shell integration and the code responsible for command autocompletion and error underlining, then trace how hash -r in bash and rehash in zsh are handled. Done means newly installed binaries become available without opening a new tab, window, or pane while preserving terminal history.

Written by the indexing model from the issue text.

Description

enhancement triaged
Discord username (optional)

0x766c6164 #7434

Describe the solution you'd like?
As the docs mention, 

>Newly installed apps will trigger error underlining until you open a new Warp session (Window/Tab/Pane).

However, there are many ways to update the autocompletion in shells, for example `hash -r` in bash, and `rehash` in zsh. While these commands run successfully cross-term, with Warp we're required to open a new tab/window/pane. I am one of the users that try to keep the work in as few tabs as possible - if I install a package or put something in `$PATH`, I would like to be able to continue my workflow without having to close everything (losing history).
Is your feature request related to a problem? Please describe.
I don't like having to lose terminal history (commands & output, precisely) just to be able to have tab autocompletion available for new binaries.
Additional context
image
How important is this feature to you?

3

Warp Internal (ignore) - linear-label:770f6576-d6c0-4e4f-a259-fc64b5156087

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.