RANDOM FORTUNE:

Chicago law prohibits eating in a place that is on fire.

qutebrowser is a keyboard-focused browser with a minimal GUI. It’s based on Python and PyQt5 and free software, licensed under the GPL. It was inspired by other browsers/addons like dwb and Vimperator/Pentadactyl. Homepage: https://www.qutebrowser.org git: https://github.com/qutebrowser/qutebrowser ============================================================================== This document will show how to do an alternative installation of qutebrowser for Slackware Linux using a virtual environment. The full instructions are here: https://github.com/qutebrowser/qutebrowser/blob/master/doc/install.asciidoc#tox It will be installed into a local directory of your choice, and can be either fully self-contained, or can use some of the system-wide libraries, such as Qt5. Note that using this method will not place the qutebrowser binary in your $PATH, therefore you will need to make a script to start it and either put that in your path, or run it directly. I'll include my quteb script in this directory that uses IPC to pass URLs and/or commands to the browser. Using IPC is faster than running the binary each time you click a link in another application. First you should decide where to put the qutebrowser main directory. I use ~/bin as a catchall for various binaries, but anywhere will be fine, and it doesn't have to be in your $PATH. INSTALL THE BROWSER The first task is to clone the qutebrowser git repo. Change directory to where you want to install it and do: git clone https://github.com/qutebrowser/qutebrowser This will create the qutebrowser directory containing the browser files. VIRTUAL ENVIRONMENT REQUIREMENTS The next task is to install pip and tox: http://slackbuilds.org/repository/14.2/python/pip/ http://slackbuilds.org/repository/14.2/python/tox/ The easiest way to install these is by using a frontend like sbopkg. I won't be going into any detail on its usage here. Tox requires pluggy, py, six, virtualenv, and setuptools-scm, so you might want to build a queue file for sbopkg to use: sqg -p tox This can then be loaded into sbopkg and installed. BROWSER DEPENDENCIES Once pip and tox are installed you need to decide what kind of virtual environment you want. The completely self-contained qtwebengine doesn't have support for proprietary codecs. If you want the browser to have those then you will need to install Qt5 system-wide and make sure to choose the option to use those codecs when you run the SlackBuild (the Qt5 readme shows how). If you want to try the webkit backend you will also need qt5-webkit-annulen, which is a fork of qt5-webkit, but is more up-to-date and contains bug and security fixes. Qutebrowser's webkit backend code does not work with the normal qt5-webkit. http://slackbuilds.org/repository/14.2/libraries/qt5-webkit-annulen/ Please see https://github.com/annulen/webkit/wiki for more info. Currently the webkit backend has a few more configuration options available than the webengine backend (the default), but not many. Webkit is a dependency of python3-PyQt5 so you will need one of them either way. The backend is chosen at run time and doesn't require a rebuild of the browser to try them both out. CREATE THE VIRTUAL ENVIRONMENT cd into the qutebrowser directory created by the git clone. For a self-contained environment run: tox -e mkvenv-pypi To use Qt5 and python3-PyQt5 that is already installed system-wide run: tox -e mkvenv The commands create a .venv directory containing libraries and a python3 binary. If you update the git repo at any time then you should recreate the .venv by rerunning the command including a -r flag. DOCUMENTATION You will need to build the documentation for the :help page and subpages. Run: scripts/asciidoc2html.py You should do this whenever the git repo is updated. :help will still work, but you will get a warning if you access the docs and they are out-of-date. RUNNING THE BROWSER The browser can be started by running: /path/to/qutebrowser/.venv/bin/python3 -m qutebrowser STAYING UP TO DATE To update the browser use normal git commands to fetch and pull from within the main qutebrowser directory: git fetch --tags git pull Rebuild the documentation as described above. Rebuild the venv as described above. If Qt5 and/or other dependencies are updated then also update the venv if you used the non self-contained approach. There may also be updates available through pip/tox for use with the self-contained method so it's perhaps worth running a regular rebuild from time-to-time. I expect these updates are documented somewhere... Answers on a postcard please... AND CONCLUDING See #qutebrowser on freenode. Well that's all there is to it. Happy browsing. LINKS THAT MAY BE OF INTEREST Privoxy homepage: https://www.privoxy.org This is a great web filter. Can take out all sorts of nasties and can route to different proxies by URL patterns. Works nice with 3proxy and tor. SlackBuild: http://slackbuilds.org/repository/14.2/network/privoxy/ 3proxy homepage: https://3proxy.ru A really nice free proxy. No, it's not squid, but it supports creating multiple proxies, works well and it's 10x easier to setup if you just need something simple that supports http, socks, routing by port number etc. SlackBuild: http://slackbuilds.org/repository/14.2/network/3proxy/ A handy site that shows your tor exit node: https://www.whatismypublicip.com (Also see my IPNotes.js greasemonkey script that cleans up this page and hides irreverent bits. There are others, but this one was easiest to 'clean' and had less js/google analytical crap^H^H^H^Hcode in it. It also has a nice map, if you feel like going hiking and can read a compass.) Youtube's html5 test page: https://www.youtube.com/html5 This will show if you have all the proprietary codecs working. 7 ticks wins the jackpot. Apparently I'm writing this from Vern-sur-Seiche, France. I thought it had warmed up a bit.

Filename Size Modification Time
greasemonkey/ Directory 2018-06-29 13:57:04
quteb 1 KB 2018-06-22 04:07:19