Colouring logic and other adaptations for Windows not applied under WSL
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.2k
- Forks
- 510
- PR merge metrics
- No merged PRs in 30d
Description
I can see from #712 that on Windows, lsd has been adapted so that it doesn't just colour every file on a Windows system as if it is executable.
However, when using lsd in a Linux distro via Windows Subsystem for Linux, the old behaviour is still present when browsing the "Windows side" of the file system.
In the screenshots you can see what I mean; they show two clones of the same repo, on the Linux part of the filesystem:
and on the Windows part:
I installed lsd for Windows too to check and in Powershell the colours are the correct ones for the same folder on the Windows side:
Ideally, for consistency, whatever logic is applied for the Windows version of lsd would also be applied to Windows files in WSL.
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
Start by reading the Windows adaptation discussed in issue #712, then reproduce the colouring difference in WSL while browsing files on the Windows side of the filesystem. Compare that behavior with native Windows lsd and determine whether the same logic applies under WSL. Done means Windows files in WSL receive consistent colouring and the behavior is verified against the reported examples.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100