micro-editor / micro-editor/micro
Micro puts stuff into $XDG_CONFIG_HOME that doesn't belong there
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 29.6k
- Forks
- 1.4k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 10
Description
From what I understand, XDG_CONFIG_HOME is for configuration files, like settings.json and bindings.json.
However in my case micro misuses that directory to place some other autogenerated files in there:
$ tree -a ~/.config/micro
micro
├── backups
│ └── %Users%bartek%projects%cg-t01-g12%blah
├── bindings.json
├── buffers
└── settings.json
3 directories, 3 files
I think stuff like backups and buffers doesn't belong to XDG_DATA_HOME. Instead they should be in $XDG_STATE_HOME (or maybe $XDG_DATA_HOME?).
Specifications
Micro version
$ micro --version
Version: 2.0.13
Commit hash: 68d88b57
Compiled on October 21, 2023
OS
$ sw_vers
ProductName: macOS
ProductVersion: 14.4
BuildVersion: 23E214
Terminal
iTerm2 (build 3.5.0beta19)
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
No source files, tests, or entry points are named. Trace Micro's handling of the XDG_CONFIG_HOME paths for backups and buffers, then review the XDG directory specifications and existing path behavior. Done means the generated files use an appropriate data or state directory without breaking existing editor behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100