Re: [Ranger-users] ranger is not restoring my terminal settings

[Gary Johnson]

On 2013-03-17, Roman Z. wrote:
> On Sun, Mar 17, 2013 at 11:33:27AM -0700, Gary Johnson wrote:
> > That was pretty easy.  Thanks for the clear instructions.  The last
> > two bisect commands looked like this:
> > 
> >     address@hidden $ git bisect good
> >     Bisecting: 0 revisions left to test after this (roughly 1 step)
> >     [172591f762e9b7f67f7e8e3649a9a6c1066528a3] widgets.browsercolumn: check 
> > if file was copied or cut when drawing
> > 
> >     address@hidden .../ranger-git/ranger $ git bisect bad
> >     Bisecting: 0 revisions left to test after this (roughly 0 steps)
> >     [b34807bd428bbe7bb40e8798af17f0f4cf5ecf1f] gui.ui: more portable 
> > terminal title support
> > 
> > and the resulting ranger.py was good.
> 
> Thanks for going through the procedure, but it seems like you didn't
> finish. Type in "git bisect good" again; the output that follows is the
> most important one.

Sorry.  I thought "0 revisions left" and "roughly 0 steps" meant it
was done.  Here is the output from the next step.

    address@hidden $ git bisect good
    172591f762e9b7f67f7e8e3649a9a6c1066528a3 is the first bad commit
    commit 172591f762e9b7f67f7e8e3649a9a6c1066528a3
    Author: hut <address@hidden>
    Date:   Sat Nov 10 17:08:41 2012 +0100

        widgets.browsercolumn: check if file was copied or cut when drawing

    :040000 040000 c1d005fd7118240eded75c43c71520061e99167f 
1bcd69aa769d0276b6c9d4b6850bc07b6c69a466 M  ranger

Regards,
Gary