lxml reports the line and column of parse errors, but by default these appear at the end of the preformatted msg - which is confusing because ST shows the line and column of the text caret in the status bar immediately after the xpath status text, and does so in the same format. This PR changes the way the XML parsing error is displayed in the status bar so that this information won't be at the end of the message.
In addition, there is now a setting called show_xml_parser_errors which can be set to false to not show the error in the status bar. This can be useful when multiple xml related plugins are installed, and a different one also shows the parse errors.
lxml
reports theline
andcolumn
of parse errors, but by default these appear at the end of the preformattedmsg
- which is confusing because ST shows the line and column of the text caret in the status bar immediately after the xpath status text, and does so in the same format. This PR changes the way the XML parsing error is displayed in the status bar so that this information won't be at the end of the message.In addition, there is now a setting called
show_xml_parser_errors
which can be set tofalse
to not show the error in the status bar. This can be useful when multiple xml related plugins are installed, and a different one also shows the parse errors.This was reported in https://github.com/rosshadden/sublime-xpath/issues/32