Cannot `lsd ~` on windows
Open
Nobody has claimed this yet.
kind/feature
need-more-info
open-for-vote
os/windows
- Dominant language
- Rust
- Stars
- 16.2k
- Forks
- 510
- PR merge metrics
- No merged PRs in 30d
Description
- os: Windows 10
lsd --version:lsd 1.0.0echo $TERM: PowerShell 7echo $LS_COLORS: -
Expected behavior
The same as ls $env:HOME
Actual behavior
lsd: ~: The system cannot find the file specified. (os error 2).
Notes
It appears that lsd supports globs itself on windows, I would expect it to do the same for other common shell shorthands like ~ that powershell doesn't expand itself.
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
Reproduce lsd ~ on Windows PowerShell and compare it with ls $env:HOME. Trace the Windows argument and path handling, including the existing glob support. Done means ~ resolves to the home directory on Windows and the behavior is covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 38/100