Franco A. Cortesi writes:
> 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
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
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
