On Sat, Oct 25, 2014 at 11:19 PM, Fluid Dynamics <a2093...@trbvm.com> wrote:

> This is a really weird one, when you think about it. How the heck does a
> programmer make a mistake that results in the *file save* function going
> into an *infinite loop*? At least it didn't go into an infinite loop
> filling my filesystem...
>

You're making a pretty big assumption that the bug happened in the file
save function.  By your own admission, the file was saved perfectly fine,
so perhaps after the file was saved it triggered a screen refresh or a
project reload or a rescanning of the files in your directory, or any
number of things that could have hung due to something specific on your
system like a lack of sufficient memory or some file locked by another
process, or whatever.

You're also making a big assumption that this is a bug in counterclockwise,
and not a problem with Eclipse itself.  I wouldn't exactly call Eclipse a
rock-solid development environment.

I understand why you feel freaked out, because it is extremely disturbing
to potentially lose work, but there's not much of a foundation here for
your fear that the integrity of your data was put at risk, at least, not
any more so than any other random crash that can happen when using any
modern IDE, or, say, a power outage or hard drive failure.

As others have said, source control is one of your best protections against
many types of failure.  In the meantime, this definitely seems worth
reporting, through proper channels, if you genuinely care about making the
product better.  Although you say you only got a stacktrace, Eclipse logs a
lot of information about what it is doing.  Laurent could probably guide
you through the process of sending him a copy of the log so he can see
exactly where the failure occurred.  Of course, if you don't really want to
make counterclockwise better, then just move along and try a different
development environment -- there are several to choose from.  In my
experience, Emacs, as one of the oldest development environments, is one of
the most stable environments I've ever used -- I've kept Emacs open for
weeks without it ever glitching.  So if that's the most important thing for
you, try Emacs.  Ultimately, I decided I just don't like Emacs, and now I'm
a happy Counterclockwise user.

-- 
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.

Reply via email to