On 29.01.2016 10:54, Florian Bruhin wrote: > There isn't. You'd typically do this via an userscript, and > there's currently no way for an userscript to request more > information (or get "answers" to commands it sends). > > qutebrowser could expose this information to userscripts via an > environment variable, e.g. some $QUTE_TABS variable set to > something like: > > 0 0 url title of first tab in first window 0 1 url title of second > tab in first window [...] > > The problem with that approach is that it might be too much data > for an environment variable, so maybe $QUTE_TABS would need to be > a filename of a temporary file, like $QUTE_HTML and $QUTE_TEXT is. > > Then again I'm not sure how much it makes sense to shoehorn all > possible usecases into somewhat fragile userscripts. I'd rather > see plugins written in Python (or possibly JS at some later point), > but it might still take a while until that's ready.
Thank you very much for your explanation. I agree that the most robust way would be the integration into the autocompletion module (or as a plugin). Stefan
