I use :bind in the browser to change my keybindings. It is unlikely that I had capslock on, but even if I did, J and K weren't supposed to be bound to that. I didn't submit a crash report when this happened; can I still do so now?
On Wed, May 9, 2018, 7:19 AM Ryan Roden-Corrent <r...@rcorre.net> wrote: > > Out of nowhere, "j" and "k" on qutebrowser started working as :tab-prev > and > > :tab-next instead of scrolling down and up. Then, I pressed another key > > Any chance you had capslock on? > > > Upon re-startup, all my custom keybindings (of which I have many) were > > reset! > > How did you configure your keybindings? Using config.py or running > `:bind` in the browser? > > -Ryan > > On Wed 05/09/18 10:05AM, Florian Bruhin wrote: > > Hey, > > > > On Tue, Apr 03, 2018 at 10:51:21AM -0400, Jonathan Saunders wrote: > > > Out of nowhere, "j" and "k" on qutebrowser started working as > :tab-prev and > > > :tab-next instead of scrolling down and up. Then, I pressed another key > > > ("a", I think) and the browser crashed. Upon re-startup, all my custom > > > keybindings (of which I have many) were reset! > > > > > > Has anyone else experienced this issue? Or, did I not catch the news > that > > > the latest version resets keybindings or something? > > > > > > I'm running qutebrowser v1.2.1-1 on Arch Linux. The last update I > performed > > > was a day ago... > > > > That sounds weird! No clue what happened there... Did you submit a crash > > report with that crash? > > > > Florian > > > > -- > > https://www.qutebrowser.org | m...@the-compiler.org (Mail/XMPP) > > GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc > > I love long mails! | https://email.is-not-s.ms/ > > >