[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Ranger-users] ranger is not restoring my terminal settings
From: |
Gary Johnson |
Subject: |
Re: [Ranger-users] ranger is not restoring my terminal settings |
Date: |
Sun, 17 Mar 2013 13:02:43 -0700 |
User-agent: |
Mutt/1.5.20 (2009-06-14) |
On 2013-03-17, Gary Johnson wrote:
> 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
I'm not doing very well at this. I think I corrupted the bisect
state before obtaining that last result. I execute 'git bisect
reset' and repeated from 'git bisect start master v1.5.0' and got
this result instead:
address@hidden .../ranger-git/ranger $ git bisect bad
b34807bd428bbe7bb40e8798af17f0f4cf5ecf1f is the first bad commit
commit b34807bd428bbe7bb40e8798af17f0f4cf5ecf1f
Author: hut <address@hidden>
Date: Fri Nov 9 21:57:52 2012 +0100
gui.ui: more portable terminal title support
:040000 040000 825a84cb428f7d6145b940fc03581160a266acc1
c1d005fd7118240eded75c43c71520061e99167f M ranger
I tried again a third time with the same results as the second time.
Regards,
Gary
- [Ranger-users] ranger is not restoring my terminal settings, Gary Johnson, 2013/03/17
- Re: [Ranger-users] ranger is not restoring my terminal settings, Roman Z., 2013/03/17
- Re: [Ranger-users] ranger is not restoring my terminal settings, Gary Johnson, 2013/03/17
- Re: [Ranger-users] ranger is not restoring my terminal settings, Gary Johnson, 2013/03/17
- Re: [Ranger-users] ranger is not restoring my terminal settings, Roman Z., 2013/03/17
- Re: [Ranger-users] ranger is not restoring my terminal settings, Gary Johnson, 2013/03/17
- Re: [Ranger-users] ranger is not restoring my terminal settings,
Gary Johnson <=
- Re: [Ranger-users] ranger is not restoring my terminal settings, Roman Z., 2013/03/17
- Re: [Ranger-users] ranger is not restoring my terminal settings, Gary Johnson, 2013/03/17