This is a common windows problem. On Thursday, January 23, 2014 9:17:09 PM UTC-5, Cedric Greevey wrote: > > [meta, but about something apparently triggered by the message, from this > thread, that I'm quoting] > > Why did reading this post cause gmail to go bonkers? I saw this thread had > new articles since earlier today, brought it up, and read the previous > message, then just after I'd scrolled down to this one, leaned back, and > started reading it the browser just suddenly began spinning on its own and > navigated by itself. Apparently about 10 seconds after I sat back > *something* input a click on the little down-triangle in the upper right > corner of the page and then clicked "sign out" because it went to the gmail > login page. And a second or so before that the chat thingy at the left > crashed as a popup there distracted me by appearing suddenly and saying > something like "Oops, problem connecting to chat". > > I don't like having my stuff suddenly go spinning out of control like > that. I wasn't touching the keyboard or the mouse at the time. The browser > should not have done anything but sit there patiently displaying this page > until *I* *CHOSE* to navigate away from it. If there is something in your > message that hijacks the browsers of people reading it, then I would like > you to know that I consider such a thing to be extremely poor etiquette and > in extremely poor taste. Do not do it again. If it was not that particular > message then I'd like to know what *did* reach into *MY* computer and start > issuing instructions on *MY* behalf *without* *MY* permission, and how to > stop that from ever happening again. This is *MY* copy of Firefox and it > goes where *I* say it does, when *I* say it does it, and not a moment > sooner. Is that absofrickinglutely clear? That is non-negotiable. Anyone > who willfully violates this edict *will* be added to my spam filter and I > will not see any future post by that author. Is *that* clear? > > > > > On Thu, Jan 23, 2014 at 7:21 AM, t x <txre...@gmail.com <javascript:>>wrote: > >> Hi, >> >> * This is the time I've heard "the one who's feeding the channel is the >> one in charge of closing it" -- previously, my channel code was fairly >> ad-hoc and agressive (since I need to kill many (go-loop [msg (<! ... )] >> (when msg ...)) blocks). >> >> * I still feel this breaks the "conveyor belt" metaphor -- when a >> conveyor belt shuts down, it's understandable that we after we take what's >> on the belt, in future takes, we get nothing. >> >> However, when putting items on a stopped conveyor belt, messages should >> not just *poof* vanish into the void. :-) >> >> * This existing semantics makes debugging annoying (perhaps this is due >> to my lack of skill). When something should be happening, and nothing is >> happening, I'm basically going around hunting for "where did I do a put on >> a closed channel", whereas if it threw an exception of some form, it'd be >> easier to handle then this "silent fail." >> >> >> >> >> On Thu, Jan 23, 2014 at 3:50 AM, Meikel Brandmeyer (kotarak) < >> m...@kotka.de <javascript:>> wrote: >> >>> Hi, >>> >>> probably the idea is, that the one who's feeding the channel is the one >>> in charge of closing it. After all, they know when there is no more input >>> available. Do you have a use case where this problem manifests? Or is that >>> just a vague fear that it might happen? >>> >>> Kind regards >>> Meikel >>> >>> -- >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Clojure" group. >>> To post to this group, send email to clo...@googlegroups.com<javascript:> >>> Note that posts from new members are moderated - please be patient with >>> your first post. >>> To unsubscribe from this group, send email to >>> clojure+u...@googlegroups.com <javascript:> >>> 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+u...@googlegroups.com <javascript:>. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> >> -- >> -- >> You received this message because you are subscribed to the Google >> Groups "Clojure" group. >> To post to this group, send email to clo...@googlegroups.com<javascript:> >> Note that posts from new members are moderated - please be patient with >> your first post. >> To unsubscribe from this group, send email to >> clojure+u...@googlegroups.com <javascript:> >> 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+u...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > >
-- -- 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/groups/opt_out.
