Some of the settings described in the configuration.md file are said to be editable by ReText only, not by the user. Therefore, it makes sense to store them in separate files.
One possible scenario would be if the user wanted to save their configuration. Now they can save the ReText.conf file and use it on another instance of ReText without affecting the config entries that should not be user editable. I came across this issue when I wanted to save the ReText.conf file to be tracked by my dotfiles repository, but I had trouble with the recentFileList entry, since I did not want to track those.
There are still some issues with this implementation. One of them is that the cache file is created with the same QSettings class as the main config file and its name does not perfectly match its intention.
mitya57
commented
2 years ago
Some of the settings described in the
configuration.mdfile are said to be editable by ReText only, not by the user. Therefore, it makes sense to store them in separate files.One possible scenario would be if the user wanted to save their configuration. Now they can save the
ReText.conffile and use it on another instance of ReText without affecting the config entries that should not be user editable. I came across this issue when I wanted to save theReText.conffile to be tracked by my dotfiles repository, but I had trouble with therecentFileListentry, since I did not want to track those.There are still some issues with this implementation. One of them is that the cache file is created with the same QSettings class as the main config file and its name does not perfectly match its intention.