2009/2/11 Keith Hubbard: > > björn wrote: >> If it is that consistent then it would be great if somebody could do a >> bisection with Git to find the exact commit where it happened. I had >> a look at the commits between 40 and 41 but I can't "guess" which one >> might be the offending commit. Does anybody with this problem know >> how to do this and have time? (I still can't reproduce reliably but >> it has happened once or twice.) >> > > It looks like this is the culprit: > > 662aa32b399c1149daa1cd3a2b5bccc8e75f589a is first bad commit > commit 662aa32b399c1149daa1cd3a2b5bccc8e75f589a > Author: Bjorn Winckler <[email protected]> > Date: Wed Jan 7 20:19:44 2009 +0100 > > Prune unnecessary code, clarify comment
Thanks Keith, that gives me somewhere to start looking. I don't see that this commit is directly to blame...there seems to be some other problem related to detection of "untitled windows" and launching processes so I'll have to dig deeper. It is weird too...right now I have one instance of MacVim open where reactivation fails every time, but when I build a new version and run it from Xcode then I cannot for the life of me reproduce the bug. Hmmm...I should be able to figure it out now though. Thanks, Björn --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_mac" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
