0

I have created a custom syntax file for Smalltalk/X - smalltalk embedded with C.

The highlighting file is mostly correct (still needs some love, but that is out of the scope of this question).

I have encountered weird limit on file size. Every file less than or equal 100.00kB has corrected highlighted syntax.

Every file larger (or equal) than 100.01kB has simple coloring.

The question

Is there an option which would allow me to fully color larger files? (I tried to search everywhere but could not find anything like it).

Edit - adding samples of the fully colored file and less colored (the difference is 1 Byte)

The fully colored looks like this:

fully colored Smalltak/X syntax

Link for it is here

The improperly colored one:

Not fully colored

Link for it is here

6
  • 1
    There should be no file size limit on the size of files that get syntax highlighted; in fact there is an open request to turn off syntax highlighting for large files because they slow performance. Can you provide some sort of link to a larger file that doesn't seem to highlight properly?
    – OdatNurd
    Commented Aug 3, 2018 at 18:45
  • @OdatNurd I see. That would make sense for huge files. I have added information (screenshots with links below) to my question.
    – tukan
    Commented Aug 6, 2018 at 15:07
  • @OdatNurd any ideas?
    – tukan
    Commented Aug 20, 2018 at 9:34
  • Sorry, I don't frequent Stack Exchange very often. Both of those files syntax highlight the same for me. However Sublime reports that it doesn't know what encoding the file is and falls back to Windows 1252 as the encoding. Using meld to see what's different reports an encoding conversion error. So possibly if your encoding is set incorrectly for the file it's confusing the syntax highlighting.
    – OdatNurd
    Commented Aug 23, 2018 at 17:17
  • @OdatNurd No worries, I'm really happy for your help. I'll double-check the encoding and check it with meld.
    – tukan
    Commented Aug 24, 2018 at 9:28

1 Answer 1

1

First thank you @OdatNurd with the question!

The answer is that the encoding confused the syntax highlighting and when it it fixed everything works as expected.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .