Florian Bruhin

Completion for commands

2

Likely it's already possible to pass a completion function to a new command, but it should be documented.

https://github.com/qutebrowser/qutebrowser/issues/521#issuecomment-452302983

- [x] Tab API - [ ] webelement API - [ ] enums and such: `ClickTarget`, `JsWorld`, `InitContext` - [ ] api.cmdutils - [ ] api.config - [ ] api.downloads...

Users should be able to blacklist extensions (even builtin components) from loading.

So we can make e.g. `qute://pyeval` into an extension. Not sure yet about how to namespace things - maybe a separate `qute-ext://` scheme?

The main usecase obviously being [qutenyan](https://gitlab.com/jgkamat/qutenyan)!

Getting all windows, getting tabs from them, signals for new windows/tabs etc. Should probably allow moving most `:tab-*` commands to use the tab API.

Extensions should be able to add their own settings to qutebrowser.

Custom excluding in recursive mode

3

Right now it looks like `.ipynb-checkpoints` is excluded when using `black_nbconvert .`, but that include is hardcoded. This means when e.g. using it via [tox](https://tox.readthedocs.io/) (or from a hand-created virtualenv),...

Update help, and let kitty download the image by itself.