Protocool ack-tmbundle

Comments and changes to this ticket

• 

  Trevor Squires November 2nd, 2009 @ 07:31 PM

  It's not a known issue that I recall and I've never personally had issues with being unable to load the cgi module.

  Which leaves me only able to take a stab in the dark... I guess the first thing I'd check is to make sure your standard ruby is, in fact, standard. Does 'which ruby' from the shell point to /usr/bin/ruby?

  After that, I'd check whether this works from the command line:

  ruby -rcgi -e "puts :works_okay"

  If that raises the LoadError then something is amiss with your ruby installation - there should be a cgi.rb file in /usr/lib/ruby/1.8 (assuming the standard ruby install) that is probably missing.

  If that doesn't raise the LoadError then I'd wonder if you have TM_RUBY set in TextMate (under Preferences / Advanced / Shell Variables) that is pointing to a ruby installation that doesn't have cgi.rb.

  Regards,
  Trev

• You flagged this item as spam.
  

  Vidal Graupera November 3rd, 2009 @ 02:13 PM

  Hi,

  Thanks for quick response. I have the same problem on 2 different machines both running the same textmate version and snow leopard 10.6.1.

  I tested those commands

  which ruby => /usr/bin/ruby

  ruby -rcgi -e "puts :works_okay"
  works_okay

  Yes, I have a cgi.rb in /usr/lib/ruby/1.8

  I checked and I don't have TM_RUBY set. I went ahead and set it to /usr/bin/ruby but that didn't make a difference.

  Vidal.

• 

  Trevor Squires November 3rd, 2009 @ 02:46 PM

  sigh - I'm afraid I'm at a complete loss then - you're running the exact same TM version and OS version as me, but I can't reproduce your issue.

  I wish I could be more helpful... sorry.

  Trev

• You flagged this item as spam.
  

  Vidal Graupera November 3rd, 2009 @ 10:58 PM

  I am wondering whether it is some other gem that I have installed or something on my path which is different that yours...

  FYi,, I saw this too, http://groups.google.com/group/ack-users/browse_thread/thread/246d2....

• You flagged this item as spam.
  

  Vidal Graupera November 10th, 2009 @ 10:34 PM

  You can close this out. The error message is deceiving. I went into the bundle directory and tried to execute the ack-standalone.sh from the command prompt manually. I discovered that I had git misconfigured and it had messed up this file by adding CRLF's to it which prevented it from executing correctly.

• 

  Trevor Squires November 11th, 2009 @ 04:46 PM

  • State changed from “new” to “resolved”