You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am playing around with this extension and I am generally impressed by the functionality, which leads me to recommend VSCoce as a viable alternative to oXygen for editing XML files with bi-directional content. However, when I am editing a rather large XML file of some 5,5 MB (a TEI-encoded bibliography of more than 3500 entries), suggestions take about 5-10 seconds after typing the opening bracket <. I assume that the problem is that in the background the extension re-validates the XML because typing < invalidated the document (wellformedness is obviously violated). It would be great if one could turn off continuous validation for this purpose.
Another benefit of such an option would be massive energy savings and thus improved battery life even on modern laptops. Editing said XML file, my recent 15" MacBook Pro uses 300% CPU cycles for VSCode and the extension, quickly draining the battery.
The text was updated successfully, but these errors were encountered:
HI @tillgrallert, thanks for reporting this! The next release will have a configuration file, so I'll experiment with adding an option for this. The extension uses a SAX approach for autocompletion, so it will still need to parse the file up to the cursor in order to provide suggestions, which means the 5-10 sec problem may not get much better even without continuous validation. But hopefully it will at least reduce CPU usage.
I am playing around with this extension and I am generally impressed by the functionality, which leads me to recommend VSCoce as a viable alternative to oXygen for editing XML files with bi-directional content. However, when I am editing a rather large XML file of some 5,5 MB (a TEI-encoded bibliography of more than 3500 entries), suggestions take about 5-10 seconds after typing the opening bracket
<
. I assume that the problem is that in the background the extension re-validates the XML because typing<
invalidated the document (wellformedness is obviously violated). It would be great if one could turn off continuous validation for this purpose.Another benefit of such an option would be massive energy savings and thus improved battery life even on modern laptops. Editing said XML file, my recent 15" MacBook Pro uses 300% CPU cycles for VSCode and the extension, quickly draining the battery.
The text was updated successfully, but these errors were encountered: