Cannot create symlink to file with non-latin letters in its name
Open
Nobody has claimed this yet.
symlinks
- Dominant language
- C
- Stars
- 240
- Forks
- 60
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 1
Description
Describe the issue
ln -s Äfoo.go afoo.go command fails, even though the file named Äfoo.go exists.
Steps to Reproduce the Problem
touch Äfoo.goln -s Äfoo.go afoo.go- The command fails with message "no such file or directory"
A symlink should be created instead.
Additional Context: Operating System, Screenshots
- OS: Windows 10 Pro 21H1 with October 2021 cumulative update
It also fails with cyrillic letters in file name, and I suspect it will fail with any non-ASCII letters.
Setting MSYS=winsymlinks:nativestrict is a workaround, no such error is raised then.
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 the failure on Windows 10 with touch Äfoo.go followed by ln -s Äfoo.go afoo.go, then compare it with MSYS=winsymlinks:nativestrict. Trace the symlink-creation path used by ln -s; done means links to filenames with non-ASCII characters are created successfully without the workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100