Tried to pull the previous version from the Time Machine, but managed to do this only after I did force quit GitX. Dock right-click > Quit didn't quite impress it.

I'm running GitX 0.8.2_beta on OS X 10.6.7, and the "open in FileMerge" link in the commit details window doesn't always work. Most of the time, it works for the first listed file -- e.g., if the commit contains five files, the "open in FileMerge" link works for the first file, but not for the remaining four. But sometimes, it does work for other files -- and other times, it doesn't work for the first-listed file.

I don't know whether there's available logging I could be sending you, but if there is, please let me know how to access it...

Thanks.

Your Gitx version is amazing! I really like the changes you have made, it is a big improvement. :)

I have noticed one problem though: when I go to the "Stage" view, the app will become unresponsive, changing my cursor to a beachball. Often, this will last for 3-10 seconds. It makes it difficult to flip back and forth between Gitx and TextMate while editing and staging changes. Is there any chance that this will improve in the future? Thanks for all the new features, I am really enjoying them.

See this screenshot: http://d.pr/SlmO

I have one git-svn repo that works fine and another that has this problem.

The Console logged the following errors:
GitX[70680] Could not connect the action discussGitX: to target of class ApplicationController
GitX[70680] Unknown class PBNiceSplitView in Interface Builder file at path /Applications/GitX.app/Contents/Resources/PBGitCommitView.nib.
GitX[70680] *** -[NSCFString substringToIndex:]: Range or index out of bounds

Hi,

every time I try to open a git-svn repository, GitX crashes. If wishes, I can copy the whole error report.
This repository works fine with GitX 0.7.1 (the pieter version). I also seem to have no problem with normal git repositories.

Any idea how to fix this?

Application Specific Information:
abort() called
objc[78413]: garbage collection is ON
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[PBGitSVOtherRevItem        setAlert:]: unrecognized selector sent to instance 0x20007cee0'
*** Call stack at first throw:
(
    0   CoreFoundation                      0x00007fff88e517b4 __exceptionPreprocess + 180
    1   libobjc.A.dylib                     0x00007fff83b060f3 objc_exception_throw + 45
    2   CoreFoundation                      0x00007fff88eab110 +[NSObject(NSObject) doesNotRecognizeSelector:] + 0
    3   CoreFoundation                      0x00007fff88e2391f ___forwarding___ + 751
    4   CoreFoundation                      0x00007fff88e1fa68 _CF_forwarding_prep_0 + 232
    5   GitX                                0x000000010002b5cf -[PBGitSidebarController evaluateRemoteBadge:] + 113
    6   Foundation                          0x00007fff88f28f29 __NSThread__main__ + 1429    
    7   libSystem.B.dylib                   0x00007fff82ea94f6 _pthread_start + 331
    8   libSystem.B.dylib                   0x00007fff82ea93a9 thread_start + 13
)

Running a command like:

gitx -- somefile.cpp

Opens the file and shows the history of commits that touch that file, but attempting to click any of the commits causes the display to flicker, refresh, and then your click was ignored.

Generally it causes GitX to freeze.

You can try this with git clone -L wmit.git -- git://github.com/dak180/wmit.git wmit then try to open wmit in GitX.

I continuously get the error could not update HEAD on any git repos that I open with gitx

I seem to be having speed trouble with your releases. It works 100% on "normal" sized repos, but I have 1 with a lot of branches (30+) and it seems to make the app extremely slow. I'm not too sure if it's related to the number of branches with different commit history, or whether it's just the sheer number of commits.

A possible test case could be the source repo for the linux kernel.

I've tested with your releases and found all of them have the same problem, whereas the original releases from pieter and also brotherbard are ok, so I think the fix is some kind of regression in your patch set. I'd like to try help by bisecting the code and testing where the problem came in, but I don't have enough experience with compiling on mac to do it.

from twitter:

@donpark

@laullon I like your version of gitx. hope you keep adding to it. 1st feedback: show image as thumbnail if too big (my sketches are huge!)

I've noticed this happening in 0.8.2 (beta). If I select a commit pretty far down the list, I switch applications and switch back, now suddenly instead of looking at where I had scrolled to, the commit I last selected is now the top most item.

I tend to use GitX to view history while git rebasing so I can clean up all the commits I didn't mean to make, and it is rather annoying to get flung down to the last selected commit when attempting to select a more recent commit.

When GitX is hidden (⌘ H) and I ⌘ TAB to it, before removing its hidden status and showing the window, too much time passes (much more than any other application). This happens on both my MacBook Pro (i5) and my iMac (CD), regardless on memory or CPU usage (even though high stresses makes it more evident).

Hi

GitX crashes on start when I try to open a git repo which git svn clone. I have to branches on this repo, a develop and a master branch.

Here is an Apple crash report.

git://gist.github.com/870839.git

GitX fails to display repos if branches names contain slash (like git-flow names feature branches like feature/foobar. BrotherBard fork doesn't have this problem.

Hello. I'm a Ruby developer so it would be most useful to me to have syntax highlighting for .rb files in the "Tree View" of GitX. In GitX 0.7.1 there is no syntax highlighting for a Ruby file in Tree View. Here is a screenshot of what that looks like: http://cl.ly/1l2s3S3F1x2e1j0E1X1Z

Thanks!

I'm using git with git svn, but I'm also managing some of my own branches. Unfortunately, in SVN mode it looks like all push and rebase commands to other specific branches are disabled, and only the svn dcommit / etc commands are shown. It would be wonderful if this limitation could be removed, such that I would have access to both svn dcommit and the ability to push and rebase with respect to other specific branches.

Users should be able to rename the selected branch, remote, or tag by clicking on the already selected item in the outline view. This behavior is consistent with the UI behavior of Xcode, iTunes, Finder, iCal, and just about everything else that uses an outline view.

I tried to implement this myself a few weeks ago but ran into problems due to the fact that the NSOutlineView GitX uses is so heavily (and, IMHO, unnecessarily) customized.

Stashes don't seem to be sorted in any particular order right now, it would be more intuitive if they were displayed in stack order.

Hey, just got an git commit with "" on its body comment, and on gitx it renders a select box, and then breaking the commit diff, since select tag is not closed I believe. Didn't test with other HTML tags, but it must generate the same issue.

First of all a big thanks for all the effort going into making GitX even better and creating a graphical interface to more of git's features.

An issue I ran into when playing with the current revisions is that files with non-ASCII file names aren't handled correctly and git cannot operate on them.

For an example try:

[kalle:/tmp] ssp% mkdir test
[kalle:/tmp] ssp% cd test
[kalle:/tmp/test] ssp% git init
Initialized empty Git repository in /private/tmp/test/.git/
[kalle:/tmp/test] ssp% touch ä

Then view the repository in GitX and try to commit the file »ä«.

http://dl.dropbox.com/u/382997/GitX%20Umlauts.png

While browsing through the history of a branch, if you refresh (View -> Refresh), GitX switches from the currently selected commit to the most recent commit. This is especially problematic with the "Refresh automatically" preference enabled since you'll lose your place when you switch away from GitX and back.

It's simple enough to disable the "Refresh automatically" preference and only refresh manually when I'm no longer concerned about losing my place, but it would be nice to be able to get the timeliness of automatic refreshing without sacrificing browseability.

Simply put, "Refresh" and "Switch to HEAD on refresh" are orthogonal.

the app seems to start find, but when I try to open a repo nothing really happens.
There is console output tho:

11/03/2011 09:07:28 GitX[5951] Could not connect the action discussGitX: to target of class ApplicationController
11/03/2011 09:07:43 GitX[5951] remote.title="git-svn"
11/03/2011 09:07:44 GitX[5951] *** -[PBGitSVOtherRevItem setAlert:]: unrecognized selector sent to instance 0x80044b700
11/03/2011 09:07:44 GitX[5951] An uncaught exception was raised

11/03/2011 09:07:44 GitX[5951] *** -[PBGitSVOtherRevItem setAlert:]: unrecognized selector sent to instance 0x80044b700
11/03/2011 09:07:44 GitX[5951] * Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '* -[PBGitSVOtherRevItem setAlert:]: unrecognized selector sent to instance 0x80044b700'
11/03/2011 09:07:44 GitX[5951] Stack: (
140735359101724,
140735385659599,
140735359128667,
140735359122148,
140735359122488,
4295144911,
140735364332853,
140735351361167,
140735351360849
)
11/03/2011 09:07:44 [0x0-0x11c11c].nl.frim.GitX[5951] terminate called after throwing an instance of 'NSException'

I add files to commit, commit them and they are here, back again in Changed files list. But emprty commits were actually created.

Adding changing the libgit build script to CFLAGS="-arch i386 -arch ppc -arch x86_64" and changing the build architecture seems to be all that is needed.

It seems to do a better job of doing this correctly if I do a command+R refresh, but not always.

this bug seems to only exist in the 0.8.1 release

I renamed a file within my repository and when I tried to view it with GitX it didn't show me any output for that commit, when I selected any other commit it worked without issues.

When I went back, modified the file to update something and then git commit --amend'ed it, it showed up properly within GitX.

I can't take any screenshots as I am currently at work. These are the steps to replicate

git mv file1 file2
git commit -a -m "Moved file1 to file2"
gitx

Let me know if there is anything else you need!

Staging/ unstaging lines causes the following error:

Index Operation Failed
Applying patch failed with return value 128. Error: fatal: corrupt patch at line 28

Git version: 1.7.4.4

I have a pre-commit hook:

 rake find_mass_assignment

That's all I have here and it works just fine from the console. When using GitX (tried 0.7.1 and 0.8.1), it simply sayd "Pre-commit hook failed" even rake task exists with "0". When I try to commit the same file change within command line, it works fine.

I assume it incorrectly interprets hook exit result.

Like have an option or something

It only loads this far: http://d.pr/I79X

Hiding the toolbar, quitting and restarting GitX results in the toolbar being displaying again.

It seems that all commands that use a diff ("blame", "history", "diff with master", etc.) are broken, and have no effect.

The features used to work fine (notabily in the dgrijalva/gitx repo).

Basically, it's only displaying this: http://dl.dropbox.com/u/330142/Screenshots/ss3jmsz09_s5.png

but only on one of my repos. It's a pretty long-running repo. Doesn't happen on other repos, but if I re-clone this one from one of our remotes, it does the same thing.

Ideas?

When I add a commit using the "Commit" view, and then switch back to the "History" view, my commit is shown, but tagged as somehow being beyond "master". Even refreshing with ⌘R doesn't update the master tag -- instead, it simply scrolls the view down to the commit that is already tagged master. Here's what the view looks like before I try to refresh:

It would be really cool if GitX (L) could use a regular expression to parse teh comment text and replace some of it with clickable links. I am thinking of something along the lines of: http://trac-hacks.org/wiki/RegexLinkPlugin

Once updated to 0.8.2 version started to pop repeatedly a window asking for the SSH password, I had to uncheck Preferences -> General -> Use custom askpasswd

Thank you for your GREAT work!

Hello!

I've been trying to push some changes I've made in my projects to their repository as well as using fetch and pull to check for changes made by other people.

Fetch and Pull work fine most of the time, but using Push produces this error every time:

Pushing master to origin encountered an error.
command: git push origin master
error = 13

The pull error I get is:

Pulling all tracking branches from origin encountered an error.
command: git pull origin
error = 13

The fetch error I get is:

Fetching all tracking branches from origin encountered an error.
command: git fetch origin
error = 13

I am using v0.82 beta of your GitX(L) with Git v1.7.4.4 from http://code.google.com/p/git-osx-installer/

EDIT: If I use git fetch after I git push, I can see the pushed changes are being uploaded fine, even with the error appearing afterwards.

(Using 0.8.2beta)

For diffs that contain lines longer than can be displayed in the current window size, the file diff "blocks" extend wider than the window. This means that some information and the "Open in FileMerge" are hidden. If there are multiple files in the commit, then the diff "blocks" are sized differently, inconsistently. See http://i.imgur.com/vvtj5.png.

Some other (older) versions of GitX had consistent sizes for the diff blocks, that matched the window width. For diffs with lines longer than the window widget, there was a scrollbar per file which allows viewing all of the diff contents. See http://i.imgur.com/ylpIa.png.

Opens up http://gitx.lighthouseapp.com/tickets, should probably open up https://github.com/laullon/gitx/issues instead.

If you select a commit to see differences, and switch to another app (lets say firefox or vim ) and switch back to GitX the view is rendered again and you loose focus on your previous selected commit

For example, if a perform a commit in master, the commit appears in the history, but the 'master' label remains in the parent commit. Refreshing doesn't update it. If I switch to Commit view and back to History view it does update.

I translate stuff in some projects so it is nice to diff the docs since my last translation efforts to see what changed. I wanted to use your GitX to diff that date with Head and work in an editor. However after switching back from my editor to see more changes in the diff GitX reverted the diff view to the normal tree view. So I have to always select the file again which I want to diff when I unfocus and then refocus on GitX. Could you make the diff view sticky, please?

Regardless of what repo I open, the blame view just shows a blue bubble where the blame list should be.

I know this works in other forks of gitx; very jarring when coming from having a custom toolbar arrangement.

Perhaps I am blind but i cannot seem to find a way to make Gists from within the program (0.8.2) as the preferences suggest I should be able to do.

Versions 0.8.1 and 0.8.2 beta keep prompting for SSH Remote Login with text "???? poipoi". OS X locale is English, not other text comes out like this.

When attempting to open one of my git repos, the error below is logged in console and no visible error is presented on the screen (nothing happens) no matter what method I use to load it. This specific repo is sitting inside my Dropbox folder, so some external force could have corrupt an aspect of it, but I have been unable to find any problems and can still operate on it successfully from windows git clients (Git GUI / GitExtensions) and from command line (git-status, git-commit, git-push).

I am happy to debug this myself if necessary, but thought I would post this issue before I went about doing so in case there is an easy solution to it. At very least I believe GitX should show an error message to the user for whatever reason it is failing.

11/05/17 18:28:12 GitX[71711] HIToolbox: ignoring exception '*** -[NSCFDictionary setObject:forKey:]: attempt to insert nil key' that raised inside Carbon event dispatch ( 0 CoreFoundation 0x95f8f6ba __raiseError + 410 1 libobjc.A.dylib 0x92517509 objc_exception_throw + 56 2 CoreFoundation 0x95f8f3e8 +[NSException raise:format:arguments:] + 136 3 CoreFoundation 0x95f8f35a +[NSException raise:format:] + 58 4 Foundation 0x97ea09ab -[NSCFDictionary setObject:forKey:] + 185 5 GitX 0x00005193 0x0 + 20883 6 GitX 0x00009a59 0x0 + 39513 7 GitX 0x0000969e 0x0 + 38558 8 GitX 0x00009104 0x0 + 37124 9 AppKit 0x94605ddd -[NSDocument initWithContentsOfURL:ofType:error:] + 311 10 AppKit 0x94605981 -[NSDocumentController makeDocumentWithContentsOfURL:ofType:error:] + 383 11 AppKit 0x94605739 -[NSDocumentController openDocumentWithContentsOfURL:display:error:] + 886 12 AppKit 0x94604a24 -[NSDocumentController _openDocumentsWithContentsOfURLs:display:presentErrors:] + 3718 13 AppKit 0x9471e407 -[NSDocumentController openDocument:] + 352 14 AppKit 0x943f8c46 -[NSApplication sendAction:to:from:] + 112 15 AppKit 0x943f8af9 -[NSMenuItem _corePerformAction] + 435 16 AppKit 0x943f87eb -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 174 17 AppKit 0x943f86da -[NSMenu performActionForItemAtIndex:] + 65 18 AppKit 0x943f868d -[NSMenu _internalPerformActionForItemAtIndex:] + 50 19 AppKit 0x943f85f3 -[NSMenuItem _internalPerformActionThroughMenuIfPossible] + 97 20 AppKit 0x943f8537 -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 336 21 AppKit 0x943ecc61 NSSLMMenuEventHandler + 404 22 HIToolbox 0x97409c2f _ZL23DispatchEventToHandlersP14EventTargetRecP14OpaqueEventRefP14HandlerCallRec + 1567 23 HIToolbox 0x97408ef6 _ZL30SendEventToEventTargetInternalP14OpaqueEventRefP20OpaqueEventTargetRefP14HandlerCallRec + 411 24 HIToolbox 0x9742b7f3 SendEventToEventTarget + 52 25 HIToolbox 0x97457e87 _ZL18SendHICommandEventmPK9HICommandmmhPKvP20OpaqueEventTargetRefS5_PP14OpaqueEventRef + 448 26 HIToolbox 0x9747cb90 SendMenuCommandWithContextAndModifiers + 66 27 HIToolbox 0x9747cb47 SendMenuItemSelectedEvent + 121 28 HIToolbox 0x9747ca5d _ZL19FinishMenuSelectionP13SelectionDataP10MenuResultS2_ + 152 29 HIToolbox 0x9744c160 _ZL14MenuSelectCoreP8MenuData5PointdmPP13OpaqueMenuRefPt + 454 30 HIToolbox 0x9744b8bb _HandleMenuSelection2 + 465 31 HIToolbox 0x9744b6d9 _HandleMenuSelection + 53 32 AppKit 0x943e61a2 _NSHandleCarbonMenuEvent + 285 33 AppKit 0x943bad3e _DPSNextEvent + 2304 34 AppKit 0x943b9fce -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 156 35 AppKit 0x9437c247 -[NSApplication run] + 821 36 AppKit 0x943742d9 NSApplicationMain + 574 37 GitX 0x00002525 0x0 + 9509 38 ??? 0x00000002 0x0 + 2 )

If i select a merge commit that definitively has changes (as verfidied by git show) these changes are not shown.

If I drag two or more files from the unstaged box to the staged box, it doesn't actually stage them.

Commit will submit a blank commit and move the files back to the unstaged box.

Switching windows also moves the files back to the unstaged box, so it really seems to be doing nothing—running git status from the commandline shows nothing as being staged.

When the files are "staged" in this broken state, diff for the files is blank.

Dragging or double-clicking on a single file does stage correctly, but that means the only workaround is staging files one at a time or through commandline.

This works fine on the brotherband fork, and makes this fork pretty much unusable for me.

As of 0.8.2 notes are displayed as other refs it would be more useful to have them displayed inline in some manner.

For more info on notes you can see the github blog on it or the man page for it.