Given the level of concern, I will change the default and release a new version right away.
How does this coincide with the 3.1.1 release though? I was still on 3.0.15 and there are new features and other fixes in 3.1.x. Do the new features and the other fixes happen to be reasonably tested and ready already?
Was it really all about the “level of concern”, as you say, and you wouldn’t have changed this without the exposure?
He was (made) aware of the problem and chose to keep the default.
First made it sound like a very specific issue for that one user, and was given a way to disable it for him.
Second made it sound like an entire class of users would need it off, and an option switch was provided.
What do you think is more probable, that he intentionally left that hole open despite not directly benefitting from it, or simply that when he answered both original reports and provided an appropriate solution, he didn't fully think about the details and implications of what those issues meant?
Have you really never have a closed issue come back to you "went from bad to worse, abort!“ ?
Thanks for the amazing job you are doing on iTerm it's a joy to use.