Tab completion not working at home directory under Warp.app
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.2k
- Forks
- 510
- PR merge metrics
- No merged PRs in 30d
Description
- os: Mac OS 13.1
- `lsd --version`: lsd 0.23.1
- `echo $TERM`: xterm-256color
- `echo $LS_COLORS`:
## Expected behavior
If applicable, add the output of the classic ls command (`\ls -la`) to show the buggy file/directory.
Tab completion should work as the classic `ls` command.
## Actual behavior
If the application panics run the command with the trace (`RUST_BACKTRACE=1 lsLSD.`).
In case of graphical errors, add a screenshot if possible.
When I'm at home directory and push tab key after typing `lsd`, no suggestion would show and completion does not work.
(It should suggest 'Application', 'Download' or 'Documents' directories and so on.)
It occurs at only home directory, when I'm in another directory, the tab completion works.
And if I try the classic `ls` command, tab completion works wherever I'm at.
And this occurs at Warp.app, tab completion will work at iterm2.
That's why I have no idea which of lsd or Warp causes of this problem.
- Warp: v0.2023.01.03.08.03.stable_01
- iterm2: 3.4.19
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or entry point is named. Start by reproducing tab completion from the home directory with lsd in Warp.app, then compare it with classic ls and iTerm2 using the reported macOS, lsd, Warp, and iTerm2 versions. Done means identifying whether lsd is responsible and documenting a confirmed fix or a clear reproduction for the responsible project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100