I'm pretty sure it was all the keybindings, not just ones set during that
session. Capslock may have been involved, I guess. I will say that I
haven't had any issues since this, though, so I don't see the need to keep
responding over a month-old email!

On Wed, May 9, 2018, 1:21 PM Ryan Roden-Corrent <r...@rcorre.net> wrote:

> > J and K weren't supposed to be bound to that
>
> tab-next and tab-prev are the default bindings of J and K, so unless you
> disabled that it sounds like capslock could be the culprit.
>
> > I didn't submit a crash report when this happened; can I still do so now?
>
> I think you'll get a prompt the next time you open the browser, but if
> you've already ignored that I'm not sure. Id your systems saves coredumps
> you might be able to retrieve it, e.g. I see some entries if I run
> `coredumpctl list qutebrowser`.
>
> >I use :bind in the browser to change my keybindings
>
> Are the missing keybindings ones you set in the session that crashed? Its
> possible qutebrowser didn't get a chance to write your config. You don't
> happen to keep your configs under version control, do you?
>
> -Ryan
> - Ryan
>
> On May 9, 2018 10:47:19 AM EDT, Jonathan Saunders <
> jonat...@saunderstech.org> wrote:
> >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/
> >>
> >>
> >>
>

Reply via email to