Skip to content
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

Open
ralish opened this issue May 2, 2014 · 9 comments
Open

Redundant ConEmu.xml update #10

ralish opened this issue May 2, 2014 · 9 comments

Comments

@ralish
Copy link

ralish commented May 2, 2014

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):

-               <key name=".Vanilla" modified="2014-05-02 20:48:18" build="140422">
+               <key name=".Vanilla" modified="2014-05-02 20:52:17" build="140422">

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?

@Maximus5
Copy link
Owner

That may be if you choose to "Auto save window size/position" or "... opened tabs" on exit.

@ralish
Copy link
Author

ralish commented May 16, 2014

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).

@Maximus5
Copy link
Owner

@schlamar
Copy link

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.

@Maximus5
Copy link
Owner

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.
And this will be "fixed" of course.

@schlamar
Copy link

I guess this would still solve @ralish's problem but I opened a new issue for this: #15

@Maximus5
Copy link
Owner

Maximus5 commented Sep 5, 2014

140905

@Maximus5 Maximus5 closed this as completed Sep 5, 2014
@r3c
Copy link

r3c commented Sep 9, 2016

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?

@Maximus5 Maximus5 reopened this Sep 9, 2016
@Anutrix
Copy link

Anutrix commented Jan 13, 2019

Any updates?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants