Long file names get cut off in the autocomplete suggestion window

Open
#2,870 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

No source files or tests are named. Start by reproducing the autocomplete suggestion window with two long, nearly identical filenames in a zsh session on macOS. Trace the autocomplete entry point and verify that the full suggestions remain distinguishable and visible within the window.

Written by the indexing model from the issue text.

Description

area:shell-terminal bug os:mac ready-to-implement repro:high triaged
Discord username (optional)

No response

Describe the bug

I am unable to see the full name of the file in the autocomplete suggestion window

To Reproduce
  1. Go into a folder and create 2 files with very long names (in my example, it was around 80 characters, but this will vary depending on the size of Warp's window. For the most obvious example of the bug, make it so that both filenames are identical except for the last character.
  2. cd to the folder in Warp
  3. Write a command that will require you to input the file name (in my example, I started with ffmpeg -i)
Expected behaviour

I expected the window that shows the list of possible file matches for autocomplete to be fully visible on the screen

Screenshots
screenshot-bug
Operating System

MacOS

OS Version

13.2.1

Shell Version

zsh 5.8.1

Warp Version

v0.2023.03.14.08.03.stable_01

Additional context

No response

Does this block you from using Warp daily?

No

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.