Qutebrowser – a keyboard-focused browser with a minimal GUI
qutebrowser.org
qutebrowser.org
It's a great alternative to what's left of the Firefox genocide of extensions, where only VimFX and Saka Key exist.
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
Qutebrowser keybindings essentially have full control over the page at all times.
It's going quite slow however...
For example, Opera and Firefox support the Sidebar API, which allows essentially arbitrary HTML pages to be placed in, you guessed it, a sidebar. Chrome does not support this, because they supposedly just don't want to have sidebars in their browser (it's not exactly an unsolvable task to implement).
Overall, Firefox will support the most extension APIs, but even there not all extensions will work, because there's always going to be some APIs that only make sense in one specific browser.
Lastly, it is necessary for the extension authors to port their extension. The work they have to do for porting might often be as minimal as just repackaging, testing and then uploading to the other browser's extension webpage, but they do have to do it.
So, this is going to cut off many extensions, too. If they're unmaintained, no one's going to port them. And Mozilla has much stricter policies for telemetry, ads etc. in extensions, too, so another chunk of extensions won't get ported for that reason.
If there is a specific Chrome extensions that you care for getting ported and it's unmaintained, then you can try it with Chrome Store Foxified [1], which will do the repackaging automatically. The testing you'll have to do yourself and then the fixing of potentially broken things and uploading, that depends on the license of the extension, if you're allowed to do that.
[1] https://addons.mozilla.org/en-US/firefox/addon/chrome-store-...
I've switched to it with Pentadactyl while hoping there will be a useable API for proper Vim plugins by then.
It's mouse free nirvana.
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.
Vimium is good but one thing about Vimium annoys and I don't know a good workaround for it. If I create a new tab, the focus goes to address bar and then there is no convenient way to escape back to normal mode. I know this is a restriction due to the new webextensions. Anyone got any ideas to overcome this limitation?
The address bar autofocusing is annoying. Best advice I have is to replace your new tab page with a URL or a custom new tab extension.
Also, I devised the default keybindings with three goals in mind.
1. Common keys should be easy to reach.
2. Users unintentionally trigger dangerous commands (like close the current tab). To prevent this, I bind dangerous commands to 2 key sequences.
3. Users not being able to remember keybindings. To help users remember, I try to associate commands with an intuitive key, e.g. Zooming is mapped to z.
Saka key author
We're aiming to get Tridactyl to feature-equality with Vimium and Saka-Key by the end of this weekend. (We are runnable now, but it's not a fantastic UX)
We hope to match or exceed the current WebExtension state of the art (cVim) by the FF57 release date (Mid November).
Our longer-term roadmap depends on how responsive Mozilla are to our feature requests. They've suggested that our two most important API extensions could be merged in FF58 (Jan 2018? I forget), but we'll have to see.
If you don't want to run other WebExtensions or Firefox, Qutebrowser offers a really good solution :)
Now I wonder, where does the Penta -> Tri come from? Is it intended to be usable with three fingers? (SCNR)
Or maybe because we're only trying.
https://riot.im/app/#/room/#tridactyl:matrix.org/$1507907809...
But there's Saka Key, Vimium-FF and Tridactyl.
Sure, technically it only applies to an ethnic/political/racial/etc group of humans, but it's not _that_ far-fetched to apply it to the systematic and planned extermination of an entire group of software (in this case Firefox add-ons).
I am hopeful for Qutebrowser, though; the dev is working on an interesting approach to extending the browser without WE support by allowing "userscripts" (not the Greasemonkey-esque ones). They can be written in tons of different languages. [Relevant documentation](https://qutebrowser.org/doc/userscripts.html).
[0] http://www.macmillandictionaryblog.com/is-linguistic-inflati... ("linguistic inflation" is a term that i've been using in my own head for years without using it in conversation, so i'm glad to see others have the same complaint)
I think I sometimes confuse it with hyperbole.
For example, a person who survived an actual genocide may find your analogy to be shallow because where you’ve lost some extensions due to a browser upgrade, they’ve lost everyone they love due to them having been hacked to death with machetes, or gassed, or worked to death in forced labor camps.
I don’t know, maybe they just need to get over it?
That could better be described as a capacity for empathy, particularly in the context of genocide. "No real negative thoughts" is your assumption.
I'm reluctant to use the term, but it applies. It's 'virtue signaling' and I presume it gives people an ego boost or a rush of endorphins. I doubt they really care, or have any true investment, they just want you to know they are morally superior and their peers to see them standing up for a cause, no matter how absurd.
My conclusion is, if you seek umbrage, you will find it.
My objection is in the domain of ethics, as I think taking genocide lightly is an ethical problem for all of us (that is, for humanity, which I take to include you).
> I am ... able to say the word and not be bothered by the connotations.
Quite.
- 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).
https://addons.mozilla.org/en-US/firefox/addon/vimium-ff/?sr...
2. https://gist.github.com/dmgerman/6f0e5f9ffc6484dfaf53
Edit: formatting.
1) Vimium key bindings don't work on the new tab page, and don't work until a web page finishes loading. The Qutebrowser key bindings are more first class and built in to the browser, so you can fully trust them to work all the time.
2) Qutebrowser is much better with webpages that also implement their own key bindings. There is pass-through mode which disables all Qutebrowser key bindings (except escape to leave pass-through mode) and lets the web page interpret all keystrokes.
Unfortunately I still keep the other browser around because of compatability, but I have much more hope that Qutebrowser will eventually render pages better rather than Chrome/Vimium ever getting a better interface.
Vimium comes with a blank .html file; IIRC it's what opens when you issue a command to open a new tab by pressing `t`.
I'm spending more time with FF 57 (it's really great for my needs) so I don't remember how you would set a URL for chrome//:newtab. I think you have to write an extension that redirects (with an inline script) to the Vimium blank page. I'm on mobile so I can't confirm that.
https://superuser.com/questions/324266/google-chrome-mac-set...
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.
Hooray! This is the only reason I'm still on firefox. Is there an approximate eta?
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...
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.
Moreover it allows to script some stuff easily.
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:
Thanks for this. I really needed it.
[1] https://autohotkey.com/board/topic/1093-using-keyboard-numpa...
Mind providing me the model #?
Do you use all 22 keys?
12 key numpad on the side - 12
left and right regular buttons - 12 + 2 = 14
middle click - 14 + 1 = 15
scroll up and scroll down - 15 + 2 = 17
scroll wheel can be pushed left and right - 17 + 2 = 19
two addition buttons below the scroll wheel - 19 + 2 = 21
Every button I've listed is programmable. I made the left mouse button do something else by mistake once. That was awkward.
Also, the software it comes with allows you to program in 8 keymaps over many profiles, and it can change the profile based on what program has focus. I typically just use 2 keymaps in one profile across the few programs I have to use at work.
Just having enter, delete, backspace, tab keys, whatever on the mouse is amazing, but I also have macros programmed in for various tasks in the CAD program. I use AutoHotKey for most of the automated tasks in the proprietary software for the laser cutter.
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
I've got an Android TV, but all the browsers are a bit meh with remote.
No, it won't be as powerful as Vimperator, but should be a good bit more powerful than for example Vimium.
Congratulations on releasing v1, by the way.
Some of the adblock issue is possibly an engine problem (there's some pre-script hooks that Webkit-forks don't support).
Password autofill is something I want to take care once there's a plugin API, but there are ways to make it work (the password_fill userscript, autotyping in KeePass*).
Referrer control unfortunately isn't possible with QtWebEngine's API for now...
Zotero won't be possible, but I guess that won't exist any longer with WebExtensions either?
And Greasemonkey support is on its way: https://github.com/qutebrowser/qutebrowser/pull/3040
https://www.zotero.org/downloadbookmarklet
I'm glad that Greasemonkey support is coming, though. Will the GM scripts run in the same JS scope as page scripts?
Webkit forks also render text slightly worse for HiDPI screens and don't seem to support CSS `hyphens: auto`. Which is annoying because I really like justified text.
https://github.com/qutebrowser/qutebrowser/blob/master/doc/u...