2. https://gist.github.com/dmgerman/6f0e5f9ffc6484dfaf53
Edit: formatting.
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?