did anyone else just get screwed by the 2017.2 update?

it seems cursive disappeared, along with my keyboard shortcuts

ah ha

paging Dr @cfleming, Dr @cfleming please report to the front desk

@hagmonk Dr @cfleming reporting for duty.

\o/

I started a thread on the mailing list too … I'm suddenly cursive-less and it's scary 😉

Hehe

I’m afraid it’ll have to be 2017.1.2 for the moment, I have to add support for each version.

oh wow, I figured the last EAP build would be basically equivalent to the RC build

they make all the plugin owners bump their versions?

@hagmonk Well, you can use an open range, but then things break if they change APIs.

Cursive covers enough API surface that that would be pretty frequent.