Re: [qutebrowser] binding "hint inputs --first"

2019-02-22 Thread Florian Bruhin
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

[qutebrowser] Move current tab to new window

2019-02-22 Thread Valentin Iovene
Hi, I find it sometimes useful to move the current tab to a new window (without refreshing the page, especially if there's some media playing). Is this already do-able in qb ? Thanks, -- Valentin

Re: [qutebrowser] Move current tab to new window

2019-02-22 Thread Florian Bruhin
On Fri, Feb 22, 2019 at 10:26:47AM +0100, Valentin Iovene wrote: > Hi, > > I find it sometimes useful to move the current tab to a new window > (without refreshing the page, especially if there's some media > playing). > > Is this already do-able in qb ? There's :tab-give, but that does reload

Re: [qutebrowser] binding "hint inputs --first"

2019-02-22 Thread Franco A. Cortesi
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

[qutebrowser] binding "hint inputs --first"

2019-02-22 Thread Franco A. Cortesi
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

Re: [qutebrowser] binding "hint inputs --first"

2019-02-22 Thread Jay Kamat
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