The-Compiler

I wonder, what made you think it's a terminal browser?

Quick update on that: I just released v1.0.1 which fixes some bugs introduced in v1.0.0:

- Fixed starting after customizing `fonts.tabs` or `fonts.debug_console`.

- Fixed starting with old PyQt versions compiled against newer Qt versions.

- Fixed check for PyQt version to correctly enforce 5.7 (not 5.2).

It has basic bookmarking support built in. You might also be able to integrate it with Bookmark OS via an userscript:

https://github.com/qutebrowser/qutebrowser/blob/master/doc/u...

There's also cVim, Vimium and Saka Key FWIW.

I don't do ETAs for hobby work - possibly in my next summer holidays (~July 2018). I probably won't get to it before that, but I have no idea what I'll do in the holidays yet.

The nice thing about lock icons is that they can indicate EV certificates (extended validation, where the organization basically paid some more to be verified more thoroughly). Unfortunately that's not something I can do with qutebrowser because of missing QtWebEngine API to get that information.

Another feature is to make it obvious whether you're connected via plaintext HTTP or HTTPS. qutebrowser solves that by showing the whole URL in white/green respectively.

When you see a "broken lock" icon (i.e. when there was an actual TLS issue), you did already get a big error page you had to confirm, or (in case of qutebrowser) a prompt, so you already know there's no TLS going on, right? In that case, qutebrowser shows the URL in orange.

As for getting certificate info: Unfortunately also not possible due to missing APIs - see e.g. https://bugreports.qt.io/browse/QTBUG-49822

The Tridactyl project is working on that - Mozilla hasn't shown too much interest so far unfortunately, despite code being there: https://bugzilla.mozilla.org/show_bug.cgi?id=1215061

Out of curiosity, what addons were you missing? Anything other than NoScript/uMatrix?

NoScript will be there once there are per-domain settings, which is the next thing I plan working on:

https://github.com/qutebrowser/qutebrowser/issues/27

uMatrix is basically a superset of RequestPolicy - a stripped down version will work soon after per-domain settings, but I also plan on having a GUI similar to uMatrix:

https://github.com/qutebrowser/qutebrowser/issues/2626

https://github.com/qutebrowser/qutebrowser/issues/28

Copy-pasting an answer I've given about Vimium earlier:

I've used Vimium for some months myself, and wasn't really happy with it. The reasons why mainly boil down to how Vimium is quite limited in what it can do. For example:

- It can't change the user interface at all - qutebrowser has a much more minimal UI.

- It can't spawn external processes. In qutebrowser, you can simply hit ctrl-e while editing some text input, to edit it in e.g. Vim. Or you can use :bind ,v spawn mpv {url} to add a keybinding which spawns mpv with the current page, to watch YouTube videos in a real video player.

- As soon as you are on some special page (like the Chrome extension store, or the "new tab" page), it stops working, because it can't intercept keypresses there. (yes, I've read the other answers about that now)

- In general, qutebrowser is much more configurable and extensible. You can easily integrate it with shell or Python scripts via userscripts, and soon-ish there'll be a Python plugin API as well.

There's Vimium-FF and Saka Key at the moment:

https://addons.mozilla.org/en-GB/firefox/addon/vimium-ff/ https://key.saka.io/

Also, Tridactyl is at the planning stage and working with Mozilla on a better keyboard WebExtension API:

https://github.com/cmcaine/tridactyl https://bugzilla.mozilla.org/show_bug.cgi?id=1215061

edit: Oh, looks like Tridactyl has quite some code already. I'm not sure if it's runnable yet, though.

WebExtensions are a common extension format/API, i.e. Chrome extensions are WebExtensions.

However, each browser vendor has their own specific additions, and hopefully Mozilla will add some things addons like Vimperator would need, see e.g. https://bugzilla.mozilla.org/show_bug.cgi?id=1215061

FWIW some people from the Tridactyl project are working with Mozilla at getting a better keyboard WebExtension API for Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1215061

It's going quite slow however...

FWIW you'd still need Qt 5.7.1 and an updated fork of QtWebKit: https://github.com/annulen/webkit/wiki

However, there's usually an easy way to get an up to date Qt with QtWebEngine if you're on Python 3.5/3.6: https://github.com/qutebrowser/qutebrowser/blob/master/doc/i...

Note that QtWebKit is still being developed (and supported by qutebrowser), just not by the Qt project anymore: https://github.com/annulen/webkit/wiki

Also, QtWebEngine isn't just Blink. It's basically a stripped down version of Chromium as a library, also containing things like the network stack, the JS engine (V8), etc.

That'd be me, most of those aren't really true, or not qutebrowser's fault ;-)

> a ton of dependencies

Only Qt and a handful of small Python libraries. Granted, Qt is big.

> randomly hangs > can't handle suspending

Detailed bugreports or it didn't happen - but that's probably due to people using it with an old QtWebKit version. The latest release warns about that, and v1.0 (coming later this year) will drop support for it entirely.

> cursor blinks when not in insert mode

True - there's an issue open about it, but nobody found a way to make it not blink without other side-effects so far.

> doesn't work > Python not C > QT

¯\_(ツ)_/¯

> Lacked security features

That's mostly referring to missing NoScript/uMatrix-like features, which will come with per-domain settings later this year.

qutebrowser author here ;-)

I've used Vimium for some months myself, and wasn't really happy with it. The reasons why mainly boil down to how Vimium is quite limited in what it can do. For example:

- It can't change the user interface at all - qutebrowser has a much more minimal UI.

- It can't spawn external processes. In qutebrowser, you can simply hit ctrl-e while editing some text input, to edit it in e.g. Vim. Or you can use ":bind ,v spawn mpv {url}" to add a keybinding which spawns mpv with the current page, to watch YouTube videos in a real video player.

- As soon as you are on some special page (like the Chrome extension store, or the "new tab" page), it stops working, because it can't intercept keypresses there.

- In general, qutebrowser is much more configurable and extensible. You can easily integrate it with shell or Python scripts via userscripts, and soon there'll be a Python plugin API as well.

qutebrowser author here - I think Kickstarter (or similar crowdfunding platforms) work best when you have a given timeframe (like the 1-2 months I have once a year) and a tangible feature to advertise as part of it. For qutebrowser, that was the new QtWebEngine backend last year (https://igg.me/at/qutebrowser) and a completely new config system this year.

Only if it gets turned into a WebExtension: https://github.com/akhodakivskiy/VimFx/issues/860

I've used Vimium for some months myself, and wasn't really happy with it. The reasons why mainly boil down to how VimFx/Vimium are quite limited in what they can do. For example:

- They can't change the user interface at all - qutebrowser has a much more minimal UI.

- They can't spawn external processes. In qutebrowser, you can simply hit ctrl-e while editing some text input, to edit it in Vim. Or you can use `:bind ,v spawn mpv {url}` to add a keybinding which spawns mpv with the current page, to watch YouTube videos in a real video player.

- As soon as you are on some special page (like the Chrome extension store, or the "new tab" page), they stop working, because they can't intercept keypresses there.

- In general, qutebrowser is much more configurable and extensible. You can easily integrate it with shell scripts via userscripts (https://github.com/qutebrowser/qutebrowser/blob/master/doc/u...), and soon there'll be a Python plugin API as well.

As for Vimperator - as mentioned, that probably won't be around in its current form much longer.

Have you looked at the screenshots? It's graphical, so, no.

Could you elaborate a bit? I'm not particularly proud of the current config system, but I'm guessing what gave you trouble is more that handling fonts with Qt is an exercise in sanity... ;)

Development still was continued in Qt's own tree, but as it was mentioned, as of Qt 5.4 only bugfixes will be done.

Though at some point I plan adding a QtWebEngine (i.e. Blink/Chromium) backend to qutebrowser.

I just merged a pull request which makes things a lot easier by using MacPorts/Homebrew:

https://github.com/The-Compiler/qutebrowser/blob/master/doc/...

Nope - damn, choosing a good name with no collisions is hard ;)