I would like to recommend that geany analyses whether the file is suited to be worked within geany and otherwise informs the user.

The problem with this how does Geany know? Its a similar situation to the "should warn of big files" problem that has been raised before. What is "big" for my 4GB core 2 spinny disk laptop is a snip for someone elses 32GB 3.5Ghz i7 SSD workstation.

And "analysing" the file before/during loading is only going to slow down loading more for everybody.

From my personal viewpoint, Geany is a tool for developers, and as such the target users should be assumed to have a reasonable understanding that some operations not in the common use-case (enormous lines or massive log files for eg) are not optimised for, and so may be lower performance (from experience if not by prior consideration :-).

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.