It searchs for the first input on the screen, not in the page. I think gi is already executing that command, but because there is no visible input on the screen (when calling from the bottom of a page, for example), it says "no elements found". If I execute it manually (by using :) it really finds the first input, even if it's not visible on screen.
I'm using v1.4.2, the latest available in nixos unstable repo. Maybe it's a bug and has been fixed? Sorry, I realized that just after posting. Le ven. 22 févr. 2019 à 07:09, Florian Bruhin <m...@the-compiler.org> a écrit : > On Fri, Feb 22, 2019 at 06:48:18AM -0300, Franco A. Cortesi wrote: > > Hi. I'm new to qutebwoser, I love it but i'm struggling to solve some > minor > > problems. Now I'm trying to bind "hint inputs --first" to "gi" but > > qutebrowser keeps the old behavior when I use config.bind("gi", "hint > > inputs --first") and reload the config. If instead I bind the same comand > > to another free combination, when I try to use it I'cant. There is a > > message sying "No elements found". > > What "old behavior"? "hint inputs --first" is already bound to "gi" by > default. > > 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/ > -- www.fsoft.com.ar