Automatic reload of xml modified xml files does not clear red 'x' on bad tags

[PouncingPanda]

Open an xml file with a bad tag such as this one:

Code: [Select]

<entity.complex name='menu'>
  <entity complex file='file_sgl.sgl.menu' />
</entity.complex>

The second line should have a red circle with an 'x' through it complaining about "Expected equal sign".  Alt+Tab away from SE, fix the XML file in a different program, Alt+Tab back to SE.  The file automatically updates (my SE updates all modified files automatically without prompting me) but the red 'x' is still there.  I'm note sure how to make it go away, either.

[hs2]

'clear-all-error-markers' on cmdline clears just the markers.
But perhaps an 'xml-validate' / 'xml-wellformedness' is a better choice.
You could use the 'XML' toolbar to quickly access these commands.
I'm not sure if a re-validate on reload resp. auto-clearing error markers is a good thing for everybody.
At least I don't want the error markers auto-cleared if a source file was modified outside.
HS2

[PouncingPanda]

Hmm... seems like when the file reloads a re-validate would be a good idea.  It would be nice to have that as an option at least.

[hs2]

Perhaps the auto-validate on open option should be used also on re-load (to bound the number of options, you know).
Probably this is fine for users with this config. item set.
HS2

[PouncingPanda]

I would vote for that feature.  Thanks for your input on this.