Fork me on GitHub
#cursive
<
2018-02-12
>
Drew Verlee02:02:55

did something new roll out? i’m guessing i get updates automatically right?

shaunlebron04:02:33

you will not automatically get it yet

andrzejsliwa07:02:07

ok, I found it

shaunlebron21:02:40

@cfleming: tried out the incorrect-indentation markings by loading up the clojurescript compiler repo

shaunlebron22:02:31

three bits of feedback: - I like the annotation when hovering over the red marks - difficult to go to the next incorrect indentation to fix - I expected to be able to click the “parinfer cannot run based on incorrect indentation” status message at bottom right to show the invalid location - speed is bad on a 11k file

cfleming22:02:11

F2 should jump to the next indentation marker - that’s the standard IntelliJ “Go to next problem”

cfleming22:02:40

I’ll check the speed and see if I can improve that.

cfleming22:02:11

Re: Clicking on the status message - I don’t think IntelliJ users would expect to be able to do that (you can’t on most hints). I’ll think about a way to allow jumping to the problem - perhaps just a reminder that F2 will do it.

shaunlebron22:02:58

definitely do what’s idiomatic to the editor