> I also managed to break the RI/RDoc stuff in the process, as well as > launching debug mode and Test::Unit. I went back and fixed as much as I > could, but Markus, Martin and others I could use some help making sure > that > debugging is set up to work OK again. Chris, I tried to launch a rdebug session on linux (ubuntu) but failed. I finally could start rdebug with the necessary arguments and the communication between Eclipse and the ruby process started but then the ruby process died. Does it run on OS X? I have checked in some fixes, please review them, because I do not have an overview of the new design and it was just poking. E.g. the keys for the launch configuration seem to be defined twice, and so the launch configuration could not determine the project of the ruby file to launch.
The configuration for a default ubuntu/debian installation (apt-get install ruby1.8) is also quite awkward. You have to configure "/usr" as path to the interpreter and the default site_ruby directory does not exist. So I deleted the entry but then there were problems anyway so that I had to create the default site_ruby in order to proceed at all. Any idea how to mitigate these pains on a standard Linux installation? Thanks Markus ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
