CodeEditor sometimes doesn't do auto-indent after colon on 10.15

typemytype / drawbot

http://www.drawbot.com

Other

401 stars 62 forks source link

CodeEditor sometimes doesn't do auto-indent after colon on 10.15 #352

Open justvanrossum opened 4 years ago

justvanrossum commented 4 years ago

Need to investigate. I don't see error messages.

justvanrossum commented 4 years ago

Hm, it actually doesn't keep indentation at all at the moment.

justvanrossum commented 4 years ago

Actually, there is still bad behavior with indentation, even after #353:

After typing the definition of a method, typing return after the colon makes the cursor go to the first (unindented) column, but magically jumps to the correct indentation if you start typing.
Using arrow left/right keys from one line to the previous is behaving weirdly.

typemytype commented 4 years ago

this issue is been reported here https://forum.robofont.com/topic/757/rf-drawbot-misleading-cursor-position-in-scripting-window/13

and it seems to occur based on the selected font...

justvanrossum commented 4 years ago

this issue is been reported here https://forum.robofont.com/topic/757/rf-drawbot-misleading-cursor-position-in-scripting-window/13

and it seems to occur based on the selected font...

Ouch. Switching from Input Mono to Menlo seems to fix it for me. Pretty sure this is an OS bug. We should keep this open until this is confirmed or fixed.

justvanrossum commented 4 years ago

I can't reproduce this anymore on 10.15.3.

guidoferreyra commented 4 years ago

It seems that this issue happens with some fonts, I noticed it when using Zeitung Mono Pro on macOS 10.14.6 No new info about what ca be? Maybe is something that need to be fixed on the font?

justvanrossum commented 4 years ago

No new info. I thought I actually saw it happen again on 10.15.3, but I can't immediately reproduce it on 10.15.4. I'll try using Input Mono for a while again, and will see what will happen.

This is the first time I hear this reported on 10.14, though, so I wonder whether it's even the same issue.

Even if the behavior is caused by something in the font, it's still an OS bug IMO: I see no reason why a font should (be able to) influence indentation behavior.