eza-community/eza

bug: Windows OS error 123 when passing a path spec with long file names to eza in PowerShell

Open

#404 opened on Sep 21, 2023

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Rust (21,783 stars) (439 forks)batch import
errorserrors › runtime errorgood first issueos › windows

Description

  • The version of eza being used (eza --version) v0.13.0 and main
  • The command-line arguments you are using .\eza\target\debug\eza.exe 'C:\Program Files\'
  • Your operating system and hardware platform Windows 11

Running the above command gives "C:\\Program Files\"": The filename, directory name, or volume label syntax is incorrect. (os error 123)

Running .\eza\target\debug\eza.exe 'C:\Progra~1' works

Contributor guide

Tech stack
rust
Domain
cli
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Rust programming basicsWindows file path conventions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate how eza processes command line arguments on Windows, specifically focusing on path normalization. The error occurs when a path ends with a trailing backslash (e.g., 'C:\Program Files\'). Look at how the input path is converted to a canonical path, possibly in the 'path' module or argument parsing. Check if there's any handling of trailing separators in the 'path clean' or 'fs' utilities. Also, review the 'cwd' handling and see if the issue is related to how Windows treats trailing backslashes. Comment #3 in the issue might provide additional clues.