I completely forgot to answer these two questions~! ugh.bwmilby wrote: ↑Mon Mar 19, 2018 4:20 amI think this long line thing was a big part of your issues, but every pair of eyes helps.
---------------------
How often would something like this actually be a problem in a client application? Just curious since I have not done anything client facing in LC yet (just dev facing stuff).
.. the long line issue came 2nd, after firing up the IDE for the first time and having it disappear without having done anymore than creating the new stack.
.. it may have even come third, since the IDE crashed and disappeared after I set the break point for the debugger the first time without even having run the code yet.
.. another problem that centers on my systems in particular is that primary development of the IDE is centered on Ubuntu, while almost everything I run in production is centered on Debian (not just based, but distro's that use debian as the core).
The problem with that imho is that Ubuntu is based on Debian (testing I believe), not the other way around, but Ubuntu throws a lot of other stuff into the mix (otherwise, it would be Debian, right?
) that plain old Debian doesn't bother with. So bugs I find on these systems are probably not reproducible on Ubuntu systems, as Richard and yourself have shown in many of the reply posts made in this very thread. How often something like this would be a problem in a client application is a little tougher to answer. In my opinion, if something goofy happens one time, maybe not so bad. If something goofy happens all the time, maybe very bad. If something goofy happens after it has been working for years and years without issue, maybe your bankrupt. Unless your Ms, or Apple, although Apples been on the ropes a few times.
In case you meant how often do you have to put large text files into a client facing program, I can think of several ways that might break out.
.. your making a rich text editor (or a really REALLY rich text editor, like Richmond's lil jewel). Files could EASILY exceed 1.5 megs with a problem child typist that I'm sure you yourself has seen examples of.
.. Plain text with a lot of line wrapping - maybe your writing a .js editor (I've seen some of that code, it is like they never heard of line breaks
). After all, not everyone actually formats their code. Glad I don't have to maintain it 
.. Scraping websites - formatting websites differs from person to person as much as formatting code. Your building a wysiwyg web editor, you REALLY better be prepared for long lines and huge files of every kind of text you can think of. It isn't like the olden days of yore when I was young(er) and you just banged out html in a text editor of your choice (although I am sure some do still, I know I do).
Think about some text editors you have probably used yourself. Geany just had to handle those long lines and large files. Pretty sure Sublime, mousepad, textpad, pluma, text mate, notepad, or any other text editor could handle it just as well. And I know Lc 6 could handle it, Mc handled it, and while I didn't actually test it in Rev 2.2, my guess is it could have handled it too. I'll test that out next to make sure though
So, what I guess I'm trying to say is, when your dealing with any client, even if your program is supposed to blink twice and quit, count on them wanting it to do that in ways you will never anticipate, otherwise it could be a big problem.
) so I tested in 7.1.4 based on that premise. Unfortunately, it doesn't seem to work out that way. While 7 took marginally longer, it was not on the scale that 8.x up takes.
