Colin, I naturally did send Frederick Cheung (hope I have the name right) thanks directly, although his answer did not actually solve the problem, and reiterated advice that I also found on (IIRC) stackoverflow. He did clue me in to checking the locations of ruby, rake and gems, and I found another clue on another site, where a similar problem was documented. Of course, I thanked that person profusely. I think that's pretty much adequate, and if anyone here had solved the problem, of course I would have thanked them. I understand quite clearly how these exchanges work.
The point of my last post was that one respondent seemed more focussed on topics irrelevant to my question, made remarks that were gratuitously judgmental, and what he contributed was unhelpful to others with a similar problem. Signal to noise is important, is it not? Other than that – and with no desire to extend this uneccesarily – what point of etiquette did I miss, in your opinion? On Oct 6, 2:56 am, Colin Law <clan...@googlemail.com> wrote: > On 6 October 2010 02:08, omnivore <danfdonald...@gmail.com> wrote: > > > Solution was simple, once I found it. Change the bang line in the > > rake.rb, found via 'which rake' to point to the ruby version that > > houses the gems. Now things work. > > Don't bother thanking anyone for pointing you at the cause of the > problem. They are only in it for the money anyway. > > Colin -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
