Sublime Forum

ST2 - Slowest Performing Text Editor on OS X - in Following

#1

… scenario…

I purchased ST to be able to do projects. Project a little bigger than a smile HTML Site with a couple of hundred lines of CSS.

I currently work in C Project - the code isn’t THAT long… About 1,5 Million Characters. SO the problems is this…

1)I open the Doc in ST - (The Doc is ONE line with no line breaks. )
2) Set the syntax to C (This takes about 3 minutes until the SWOD stops and ST displays my syntax)
3) I then go to a variable and hit enter to be able to clearly see. That takes about 5 minutes to complete.

I have never seen anything like this. In either TextEdit, CODA2, xCode etc etc etc…

This has got to be a bug. Or perhaps something I am missing.

Setting syntax to XML or anything ELSE than Plaintext… Provokes this extreme issue of non-performance

Any help would be great…

0 Likes
#2

You have a 1.5 Mb C file with no line breaks? Don’t do that …

0 Likes
#3

and why exactly would I NOT do that ?

Thanks
Morten

0 Likes
#4

Because it is a really bad idea. Is this for an entry in the International Obfuscated C Code Contest?

ETA: Just to be a little more constructive - SublimeText does indeed have problems with syntax highlighting and very long lines, as has many other editors.

I checked with about 250 Kb C+±source, all on one line. Sublime opens the file in a few seconds, but syntax highlighting fails. Editing is slower than in a normal file, but not unusable. In comparison, TextMate (which uses the same syntax higlighter as SublimeText) is slower in both opening the file and editing where it takes at least a second for each key stroke to register. Both Emacs and VIM can syntax highlight the file properly, but Emacs is very slow when editing, taking several seconds for each key stroke. XCode handles best here, the file opens very quickly with correct highlighting, and editing is not too slow.

But the question remains, why would anyone do that?

0 Likes