On 28 September 2011 21:12, Nick Treleaven nick.treleaven@btinternet.com wrote:
On 28/09/2011 12:03, Nick Treleaven wrote:
@Nick, there are lots of large generated files a programmer might want to check, especially XMLs and logs, saying there is an xxxGb maximum is wrong, it depends on the machine the user has. Forcing them to have to go use another editor or to not have highlighting is bad
Sorry, I missed the bit where you said no highlighting is bad. But in that case, auto-disable works fine.
Actually I should make it clear that I am not talking about editing huge files, but displaying them and showing all the navigational assistance that we can provide. So I guess so long as the tags generated by the first run that took too long and triggered the disable are going to be still there, then disabling it is ok.
Actually that leads to the question, why is it reparsing an unchanged file after the first time anyway?
In any case, there is no xxx Gb maximum, I
just meant that we shouldn't have a document menu option that is only for disabling reparsing when it can be done automatically.
Also I'm not sure whether Scintilla handles very big files well. I don't think we need to be concerned about that.
Like molasses :) if you try to edit it that is.
Cheers Lex
Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel