Thu 14 Oct 2010 12:10:54 AM UTC, original submission:
To quote vasyabelkin's post at https://bbs.archlinux.org/viewtopic.php?pid=839615#p839615
hut, I' ve found the following exception, that is printed as is w/o any additional trace info:
Steps to reproduce: Ctrl+S to suspend the urxvt/xterm output while in Ranger, than try to kill it (I've yet found a way to describe it better, but I use "kill client" command in Awesome WM [Mod+Ctrl+C in default config], when "kill -9" does nothing & "kill -15" really kills it immediately). Than I got the message "Type Q or :quit<Enter> to exit Ranger", typed "Q" and got the exception.
Ranger version: 1.3.1 testing (latest from git, like 3 hours before)
And the follow up: https://bbs.archlinux.org/viewtopic.php?pid=840015#p840015
Python version 2.6.5
Once again I've updated the ranger-git from aur an hour ago, renamed .config/ranger directory to run with defaults, used both "source /usr/bin/ranger /usr/bin/ranger" and "/usr/bin/ranger"
The only difference in debug mode is that I don't get the message "Type Q or :quit..." & ranger just quits immediately with the same exception. 100% reproducible on my machine (Arch 64b with latest updates to all the software, no testing packages) when I try to kill it with Mod+Ctrl+C in Awesome 3.4.8 with almost default config. Note that it does not happen, if I resume scrolling with Ctrl+Q
|