kingToolbox / kingToolbox/WindTerm
[Suggestion] persistent custom config support
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 32.3k
- Forks
- 2.5k
- PR merge metrics
- No merged PRs in 30d
Description
I know that most of configs can be modified by .config file, but here comes a problem for version update. After version update, all of the modified configs are overwritten by the new default ones. I cannot just backup the older configs and replace the new ones because there might be some new configurable items in the new config files.
It'll be better to have a standalone folder, eg custom/, to store custom config and in this way I can take a backup-restore operation to keep my custom config. Thank you!
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 locating where the application's .config files are loaded, written, and replaced during version updates. Determine how a standalone custom/ folder could preserve user changes while still incorporating new configurable items, then verify the upgrade and backup-restore behavior across representative configurations.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100