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

[Roman Z.]

I've never heard of this, ever.  I'd like to ask you to git bisect the
problem, to determine the exact commit where it started.

Assuming that it works fine with ranger 1.5.0, you could do it like
this:

$ cd ranger
$ git checkout master -f  # overrides all uncommited changes to ranger
$ git pull origin master  # updates ranger
$ git bisect start master v1.5.0
$ ./ranger.py -c          # -c makes it skip loading configs
$ git bisect $X
$ ./ranger.py -c
$ git bisect $X
$ ./ranger.py -c
$ git bisect $X
..

Replace "$X" with "good" if the version worked fine, with "bad" if
ranger breaks your termios settings or with "skip" if you can't
say for certain if it works or not.

Also, throw in a "reset" command to restore the termios settings when
they break.

After roughly 8 steps, it should tell you what the offending commit is.

Roman

On Sun, Mar 17, 2013 at 12:08:24AM -0700, Gary Johnson wrote:
> I've been having a problem with "recent" versions of ranger on a
> number of the Linux systems on which I've installed it.  I'm
> guessing the problem started after 1.5.2.  In any case, the problem
> persists in the latest version from the git repository.
> 
> To avoid any mistakes with the installation process, I just cloned
> ranger from http://git.sv.gnu.org/r/ranger.git, moved aside my
> ~/.ranger and ~/.config/ranger directories and executed
> ranger/ranger.py.  When I quit ranger, my termios settings are
> messed up, e.g., characters I type are no longer echoed and newlines
> are no longer accompanied by carriage returns so that the output of
> commands such as ls stair-step across the screen.
> 
> I can show how ranger has corrupted my termios settings by using the
> 'stty -g' command, as in this example.
> 
>     address@hidden $ stty -g
>     
> 6d02:5:4bf:8a3b:3:1c:7f:15:4:0:1:ff:11:13:1a:ff:12:f:17:16:ff:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0
>     address@hidden $ ranger/ranger.py
>     address@hidden $ 
> 0:0:b0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0
> 
> I executed another 'stty -g' at the last prompt, but it wasn't
> echoed.
> 
> Another manifestation of the problem is that when I launch vim from
> within ranger to edit a file, the backspace key doesn't work--vim
> just displays ^? each time I hit the backspace key.
> 
> This behavior is consistent across several different Linux systems.
> The example above is from a system running Fedora 14.  The terminal
> is GNOME Terminal 2.32.0.  I just verified that the behavior is the
> same in xterm 260.
> 
> Regards,
> Gary
> 
>