top | item 27363064

(no title)

zbaylin | 4 years ago

Hey, Onivim contributor here. Sorry to hear about that syntax highlighting bug! It’s something we’ve received a lot of feedback on, and I know bryphe is planning on dedicating more resources to syntax highlighting fixes in the next couple of months. If you haven’t already, feel free to open an issue on GitHub (or comment on one that’s similar)! It helps us put our finger on where the editor falls short for people.

discuss

linsomniac|4 years ago

Will do. I'm so new to Onivim that I wasn't even sure if it was "a problem" or "my problem", or how to get more info on it. It could be a problem with my setup, I try to keep my workstation fairly clean, but it is a working setup so it's no plain vanilla. Thanks for the reply.

linsomniac|4 years ago

I did a bit more investigation, and found that "-f" outputs huge amounts of debugging information. In that I was able to see that after 2 movement commands it is detecting a file changed event, and the "newFiletype" is "plaintext" where it was previously "python".

It doesn't seem to happen if I rename the file I'm editing to have a ".py" suffix. "foo" suffers this fate, "foo.py" does not. Submitted to Issue tracker, didn't look like it was already in there.