micro-editor / micro-editor/micro
Fallback to `attrib` for `read-only` files on Windows
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 29.6k
- Forks
- 1.4k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 10
Description
Description
With sudo being completely out of the picture on Windows, we currently have a scenario where Micro successfully detects the file's state, but then inevitably fails when it comes to saving changes:
Trying to apply attrib -r automatically, and only then throw an error, in case of insufficient permissions, would be a more considerate approach in my opinion.
Alternatively/Optionally, a corresponding option in settings to control this behavior, with options:
auto: makes the file writeable permanently when saved for the first timeprompt: same as forQuitwith unsaved changespreserve: respects the initialread-onlystate and restores it when saved
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 tracing Micro's Windows read-only detection and save path, then identify where permission failures are reported. Test with a Windows read-only file and verify the chosen behavior, including the insufficient-permissions case; the settings alternatives in the issue may require maintainer clarification before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100