<blockquote>
<p>I would like to recommend that geany analyses whether the file is suited to be worked within geany and otherwise informs the user.</p>
</blockquote>
<p>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.</p>
<p>And "analysing" the file before/during loading is only going to slow down loading more for everybody.</p>
<p>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 :-).</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/geany/geany/issues/2094#issuecomment-468234271">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJzowFGluTFtBsuKxvKWk3ovgRjsaks5vR7mRgaJpZM4bUIJ6">mute the thread</a>.<img src="https://github.com/notifications/beacon/ABDrJ6pm35SvN9IKNPONoyoK8wnzbf2Xks5vR7mRgaJpZM4bUIJ6.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/geany/geany","title":"geany/geany","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/geany/geany"}},"updates":{"snippets":[{"icon":"PERSON","message":"@elextr in #2094: \u003e I would like to recommend that geany analyses whether the file is suited to be worked within geany and otherwise informs the user.\r\n\r\nThe 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.\r\n\r\nAnd \"analysing\" the file before/during loading is only going to slow down loading more for everybody.\r\n\r\nFrom 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 :-)."}],"action":{"name":"View Issue","url":"https://github.com/geany/geany/issues/2094#issuecomment-468234271"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/geany/geany/issues/2094#issuecomment-468234271",
"url": "https://github.com/geany/geany/issues/2094#issuecomment-468234271",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>