`j` is not highlighted as valid command

Open
#5,174 3 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
macos, rust, zsh
Domain
cli

Research direction

Reproduce the issue in a zsh session on macOS using the alias from the report, and compare it with the behavior addressed by #3056. Trace the command-highlighting and alias-resolution entry points to identify why a single-character command is rejected; done means valid j aliases and autojump shortcuts are highlighted like other valid commands, with similar single-character cases covered.

Written by the indexing model from the issue text.

Description

bug needs-info ready-to-implement triaged
Dupe Check
Describe the bug

Valid commands are highlighted (not underlined) in the command line.

However, the single character command j is not recognized as valid when it should be:

  • When a program (e.g., autojump) sets up j as a command shortcut.
  • When j is aliased to any command (e.g.,la).

This should have been resolved with #3056.

Note: While j is the only case I've encountered, similar issues might exist.

To reproduce
  1. Add an alias for j:
echo "alias j='la'" >> ~/.zshrc
  1. Start new shell session.
  2. Type j in your command line.
Expected behavior

When j is a valid command (either through autojump or as an alias), it should be correctly highlighted, not underlined.

Screenshots

https://github.com/user-attachments/assets/f1a2d674-3cc1-462d-8966-3d8acba1a606

Operating system

MacOS

Operating system and version

Sonoma 14.5

Shell Version

zsh 5.9

Current Warp version

v0.2024.07.23.08.02.stable_01

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

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.