First, this plug-in is the sole reason I use Sublime. Every IDE needs his.
I work on large projects with very large files. When I enable the "on_modify": true, the Sublime slows to a crawl. 0.5 to 5 seconds between a type and it showing on screen.
No point in disabling for large file, I might as well not use it at all.
Disabling the "on_modify" also mean re-loading the file every few minutes; annoying.
A great option would be a refresh only on file save; with I do already often enough.
So we would get a set of options like:
"enabled": true,
"on_load": true,
"on_save": true,
"on_modify": false,
"max_file_size": 0,
As an alternate solution; an optimization of only refreshing the text area that just changed; I assume the entire file (files?) are re-scan every time a key is stroked. But I do not know if this is at all possible.
Thanks for the great tool;
I.C.
First, this plug-in is the sole reason I use Sublime. Every IDE needs his.
I work on large projects with very large files. When I enable the "on_modify": true, the Sublime slows to a crawl. 0.5 to 5 seconds between a type and it showing on screen.
No point in disabling for large file, I might as well not use it at all.
Disabling the "on_modify" also mean re-loading the file every few minutes; annoying.
A great option would be a refresh only on file save; with I do already often enough.
So we would get a set of options like:
"enabled": true,
"on_load": true,
"on_save": true,
"on_modify": false,
"max_file_size": 0,
As an alternate solution; an optimization of only refreshing the text area that just changed; I assume the entire file (files?) are re-scan every time a key is stroked. But I do not know if this is at all possible.
Thanks for the great tool;
I.C.