Would somebody mind explaining to me why I just had CCW 0.28.1.STABLE001
hang with 100% CPU usage when I edited this line:
:= (= v cr))))
to this:
= (= v cr))))
and then hit control-S?
I do not ever want to see anything purportedly "STABLE" do something like
that ever again, and that goes *one trillionfold* if it's IN THE MIDDLE OF
A GODDAMN SAVE. What if my file had been corrupted, or truncated and only
the first 42 bytes of the new version written thus far, or something like
that at the moment when the hang started? Fortunately, in this instance
that had not happened and the file seems to have been saved completely just
*before* the hang. I might not be so lucky next time. That is why this
cannot be permitted to happen again, and why therefore an explanation is
required, and urgently, that I might be perfectly able to avoid triggering
this severe, showstopping, and inexcusable bug again until such time as an
0.29.1 is published that has it permanently fixed.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
