Before, the first line of a `code` element within a `pre` element had indentation/padding applied to it, creating the illusion that the line started with a space. Now, all the lines in `code` elements horizontally align.
Before, the first line of a `code` element within a `pre` element had indentation/padding applied to it, creating the illusion that the line started with a space. Now, all the lines in `code` elements horizontally align.
As there is not a file called history to cat from in $QUTE_DATA_DIR, but instead a sqlite file called history.sqlite.
Thus I changed this for sqlite3 and an inline query on the history table, extracting distinct urls. And with fprint and cat piping them into dmenu,
the rest works as always.
Previously, this userscript always assumed the user wanted to parse
the current page. However, this meant that something like `:hint all
userscript readability-js` wouldn't work. To fix this, the script now
checks if qutebrowser is in hinting mode, and sets the page to be
processed accordingly.
An alternative solution would be to rewrite this script to rely on
`QUTE_URL`+`JSDOM.fromURL` accross the board. However, using `QUTE_HTML`
when the target page is already loaded seems faster, uses less data, and works offline.
Now collects all (non-ignored) files via `git ls-files` and only skips
some binary formats.
Also adds some type annotations and fixes some newly unconvered
UK-spellings.
Since gopass 1.10, reading secrets via "gopass <secret-name>" will yield a deprecation
warning which _run_pass() will stumble over. As it turns out - even "pass" can be called
with "pass show <secret-name>", so the fix will be compatible with both gopass and pass.
Refs #5690