New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Redundant ConEmu.xml update #10
Comments
That may be if you choose to "Auto save window size/position" or "... opened tabs" on exit. |
I can confirm from testing it does appear to be caused by the "Auto save window size and position on exit" option. It'd still be really helpful though if ConEmu could more "intelligently" update its XML file only when necessary to reduce or even eliminate unnecessary updates (especially useful when the file is being stored in a VCS system and thus keeps being marked as modified). |
If you really need the timestamp stored for individual config sections (why exactly if you don't mind?), you might want to consider storing them in a separate file instead, so it can be gitignored. |
Timestamp is (and must) be used to monitoring if the key was changed. The issue is not about timestamps, but about spare updating if the Keys even they was not changed actually. |
140905 |
It seems build 160904 still updates modified timestamp for "Tasks" and all "TaskN" keys, along with "Apps" and "Colors" ones whenever some unrelated setting is changed. Is this intended? |
Any updates? |
When ConEmu is configured in portable mode and is opened and closed it will update the ConEmu.xml file with the current "modified" time. This can be quite frustrating when no other settings in the configuration have changed and you keep your ConEmu.xml file in a VCS such as Git as it will result in the ConEmu.xml file always being marked as modified.
An example from a Git diff (with no other changed lines):
I think it would be preferable that the ConEmu.xml modified timestamp is only updated if the ConEmu.xml file has actually been modified instead of always updating the timestamp every exit even if there are no actual changes. Thoughts?
The text was updated successfully, but these errors were encountered: