Activereload GitNub

Comments and changes to this ticket

• You flagged this item as spam.
  

  Deleted User April 10th, 2008 @ 11:56 PM

  • Title changed from “GitNum now gui not working at all” to “GitNub not gui not working at all”

• You flagged this item as spam.
  

  Deleted User April 10th, 2008 @ 11:57 PM

  • Title changed from “GitNub not gui not working at all” to “GitNub gui not working at all”

  Ah, sorry I am too sleepy to spell and think...

• 

  Justin Palmer April 11th, 2008 @ 12:27 PM

  • State changed from “new” to “open”

  Did you launch it from the `nub` command? Also, did you launch it in a valid git directory?

• You flagged this item as spam.
  

  Deleted User April 11th, 2008 @ 12:50 PM

  Yes, that's what I wrote in my original ticket. I followed the

  instructions closely and I am sure I ran the "nub" commands in a valid

  git repo. And the screenshot is what I got from the GitNub GUI.

  Anything else I can do to help debug that, just let me know.

• 

  Justin Palmer April 11th, 2008 @ 08:14 PM

  I completely overlooked that in your original message. GitNub isn't getting any repository information. It's possible that ENV['PWD'] isn't being set, in that case, gitnub doesn't know where to locate you're repo.

  Can you run this in IRB:

  require 'osx/cocoa'
  require '/Path/To/GitNub.app/Contents/Resources/grit/lib/grit'
  repo = Grit::Repo.new("/Path/To/Your/Repo")
  repo.commits.size
  

  Do you get any commits?

  Also, what does ENV['PWD'] return in IRB?

• You flagged this item as spam.
  

  Deleted User April 11th, 2008 @ 08:25 PM

  Well, now I tried what you told me:

  >> require 'osx/cocoa'

  => true

  >> require '/Applications/GitNub.app/Contents/Resources/grit/lib/grit'

  => true

  >> repo = Grit::Repo.new("/tmp/test")

  => #

  >> repo.commits.size

  => 1

  >> print ENV['PWD']

  /tmp/test=> nil

  >> exit

  and because all seems good I tried "nub" again and this time the GUI

  is working fine as far as I can tell. So I started thinking what did I

  change since last night and what I changed was to "git" to my PATH. So

  I removed it from PATH and the GUI is giving me the same bad results

  from the screenshot. So it seems like if nub cannot find the git

  executable, the problem appears.

  If it is expected to have git in the PATH then please ignore,

  otherwise I am sure you know what modifications to do.

  Kiril

• 

  Justin Palmer April 12th, 2008 @ 09:30 AM

  yep, git should be in your path. Glad you got it sorted!

  On Fri, Apr 11, 2008 at 8:25 PM, Lighthouse

  wrote:

• 

  Justin Palmer April 16th, 2008 @ 01:51 PM

  • State changed from “open” to “resolved”