On Apr 1, 2011, at 5:29 AM, Meikel Brandmeyer wrote: > Hi, > > On 1 Apr., 11:01, Laurent PETIT <laurent.pe...@gmail.com> wrote: > >> ;tldr means "too long, didn't read" (I discovered this recently) and it acts >> as a sort of the start of a short section at the end of a long post where >> people not having time to read it in its entirety can see a summary. > > For this case it could look like this: > > "tl;dr: I have severe responsiveness problems with Netbeans and > Enclojure. There is no obvious CPU activity, so it seems to be > something I/O related. The status message "Checking for external > changes" also points into this direction. Does someone have a similar > problem?"
Yes, I encountered such behaviour on a regular basis across many releases in my time using NetBeans (close to 2 years, which started when Enclojure was the only option for those of us that are allergic to emacs). In my experience, NetBeans does get gummed up on a regular basis, almost always while engaging in various automatic IO-intensive scanning processes: http://blogs.sun.com/netbeansphp/entry/enable_auto_scanning_of_sources http://wiki.netbeans.org/FaqScanningAndIndexingIssues The project actually has a FAQ highlighting various ways the IDE might become unresponsive: http://wiki.netbeans.org/FaqSlowNetBeans - Chas -- 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
