Vieb VS qutebrowser

Vieb Browser because it is keyboard based and very easy to move around the interface.

If you know the names of the folders in advance it's possible to make a different mapping in each of the folders to load a different file per datafolder but with the same keys. There is no variable system in Vieb, and as such there are no commands that will need or use the datafolder as an argument. This specific question would best be solved by a proper bookmark system which would load a file from the datafolder anyway, without having to build this in manually. Work on this has started some time ago, but has recently stalled: https://github.com/Jelmerro/Vieb/pull/391 If you or anyone else is up to the task feel free to pick this up again, as I don't use bookmarks at all so it's of little use to me personally, and as such have bigger priority tickets to work on in Vieb most of the time.

Please could you port Vieb? It's the only browser that really works on my old ThinkPad!

First one is related to and blocked by https://github.com/Jelmerro/Vieb/issues/257

Download the latest release from vieb.dev or github. View the changelog for details. And check the FAQ for answers to frequently asked questions and startup help.

For the time being you can keep using the extension, but once 9.0.0 is released extension support will indeed be removed. To modify the styling, you can use the new "userstyle" setting to inject custom styling into any page, the relevant commit is here. Once that version is released you can find the help for it with :help userstyle, though that isn't in any released version yet (You can always build it yourself to get it early).

In the current releases there is experimental support for it, but this will be dropped soon due to the lack of compatibility. Instead I will focus my efforts towards integrating commonly requested features, which has started with the integration of sponsorblock and darkreader. So unless by a miracle somebody will contribute a working extension integration, full extension support is not something Vieb will have. You can find more info on Github, and also suggest extensions you want to be in Vieb: https://github.com/Jelmerro/Vieb/issues/385

Extensions are hard, and the current implementation is as far as I can personally make them work, which is sadly not good enough. I'm considering dropping support altogether and implementing major ones into Vieb (such as some sort of darkreader). Extensions are such a daunting task that even implementing multiple extensions from scratch seems easier than trying to make all of them work as proper extensions, this is also the approach used for the new sourceviewer and reader view (both of which use package to render the views, but are still integrated into Vieb as if a native part of it). The current progress of making extensions work is tracked in this ticket: https://github.com/Jelmerro/Vieb/issues/130, but it's been stuck at basic extensions (such as dark reader) without GUI for a while, and even those fail to install occasionally for the most obscure and random reasons, it's just not very stable at all.

Qutebrowser literally uses the same workaround, so there's that, if it still doesn't work, blame Google, they are the ones refusing custom browsers in the first place... https://github.com/mkonig/qutebrowser/commit/311296ca8a4ae95ff2c640d6178346ae2f748192