Sorry for the zombie resurrection, but apparently nothing ever logged to the tracker on this?
I'm not worrying about it much for those filesystem trees under version control, but I imagine this could be panic-inducing for a newbie. If it's helpful I'll try to isolate what's happening in my workflow to trigger this, but it's not **that** frequent, and I can't think of anything out of the ordinary so far. The element that concerns me is that I'm getting this message even when the file contents has *not actually been modified*, as confirmed by the log pane. Perhaps the file comparison function(s) used to generate the "unchanged" log messages could be run before the one that pops up the warning message? I suspect it's the latter is triggered by attribute changes or something rather than actual content checking. Sheer speculation on my part of course. . . -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To view this discussion on the web visit https://groups.google.com/d/msg/leo-editor/-/cxZ-HRCt4CcJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
