micro-editor / micro-editor/micro
Spaces are missed by >open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 29.6k
- Forks
- 1.4k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 10
Description
Description of the problem or steps to reproduce
Hello!
If you try to open a file that has a space in its filename (i.e. >open assets/test file.json), Micro will open a file with the specified filepath up to the space (assets/test). Interestingly, autocomplete works correctly (i.e. typing open assets/test, and then pressing tab will complete the entirety of the path).
Specifications
Commit hash: 2.0.8, cfcb2e45
OS: Solus (Linux)
Terminal: Tilix v1.9.3
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 issue with >open assets/test file.json, then trace the >open command's argument handling and compare it with the autocomplete path handling. Done means opening the complete filename containing spaces instead of truncating it at the first space, with the reported reproduction working on Linux.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100