And .... the UNDO bug is back in .4 ....

Remember this bug ?

It's back in 2018.2.4 (was ok in .3). Exactly the same? Not sure. Same way to reproduce the bug? Not sure.
However it happened in a similar way, in two different sessions on two different computers.
( Basically, sometimes Undo (^Z) goes to the line where the undo has to happens and does it, instead for waiting for another ^Z,
  plus some more weirdness but sorry - today is busy )

Please, please don't tell me it will be fixed in 2018.3 ...

I chose to support JB, and pay my yearly fee gladly. I like the product and the ideas in it.

But this is at least the 4th time an annoying and strange regressive bug affects a useful feature. 
From the top of my head, we had for instance the Find which suddenly acted strangely, then the Undo, then ... then the Undo again.
Each time that happens over quite some time for what seems to be a minor bug [which has to be] fixable in a minor version.
Meaning, if not fixed in a 2018.2.5, I'll have to wait for the 2018.3 which won't be covered by my current "perpetual fallback license".

Again, I pay gladly. However, now I feel tricked.
A similar issue happened a few years ago, for which I was told (roughly) "people do bugs" ; of course we do!
But the succession of that kind of regressive small bugs, affecting a useful feature, fixed in a next major release, let me wonder...

This being said, let's be clear: I'm not saying JB injects some non-vital regression for having people stay and pay the next license, that would be a harsh accusation.

 

1 comment
Comment actions Permalink

> I'm not saying JB injects some non-vital regression for having people stay and pay the next license

I would love to see this value at least 10 times lower someday (that's our bug tracker front page for PhpStorm & IntelliJ IDEA):

The idea that we're introducing bugs intentionally is a little bit of an overthinking, to say the least.

 

> Exactly the same? Not sure. Same way to reproduce the bug? Not sure.

It would be great if you could describe the steps (as you already did once) to reproduce this & submit a new bug report to our tracker. I've checked it for any similar issue and there are none currently.

1

Please sign in to leave a comment.