From ArchWiki
Jump to: navigation, search

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.

Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어

External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

Summary help replacing me
A basic guide to installing and configuring Vimprobable: a lightweight, keyboard-driven web browser.


Vimprobable is a WWW browser that behaves like the Vimperator plugin available for Mozilla Firefox. It is based on the WebKit engine (using GTK bindings). It is a fork of the currently abandoned vimpression.

There are two versions of Vimprobable: vimprobable-gitAUR and vimprobable2-gitAUR. Now that Vimprobable2 is at version 1.0, it is considered the primary branch; development of Vimprobable1 will still recieve bugfixes, but active development will be restricted to Vimprobable2.

The first version can only be customised by editing config.h before compilation. It is pretty stable and very usable. Version 2, while also stable, is under more active development - it aims at allowing more customisation, for example through :set and :map commands.


Both versions of Vimprobable are available in the AUR.

You can install either version of Vimprobable with an AUR helper, or elect to build it yourself. In any event, the basic programming tools present in base-devel are needed in order to compile and build a package for both versions of Vimprobable.

# pacman -S base-devel


Both versions require you to make customizations in the config.h file before recompiling with

$ makepkg -efi

Additionally, Vimprobable2 will look for a configuration file called $XDG_CONFIG_HOME/vimprobable/vimprobablerc that has a number of options that can be configured without any need to recompile. You will need to create this file yourself.

A basic vimprobablerc might contain the following options:

set homepage=
set scrollbars=false
set fontsize=12
set monofontsize=10
set monofont="Droid Sans Mono Slashed"

More details on configuring Vimprobable2 can be found in the rc man page

man vimprobablerc

Within the source directory, you will find two other files that can be customized, config.h and keymap.h. As one would expect, the first contains general configuration options, such as appearance and the second allows you to set your own keybindings. Any changes to either of these files require that Vimprobable2 be recompiled before they take effect.

Tip: As per the post install instructions, you will need to copy these files from the source directory to customize them.

Details for the default keybindings and options can be found in the man page

man vimprobable


Setting a more generic user agent will make accessing some websites more straightforward. In $XDG_CONFIG_HOME/vimprobable/vimprobablerc add a useragent for a browser that the site will find more acceptable, for example:

set useragent="Vimprobable2 (X11; U; Unix; en-US) AppleWebKit/531.2+ Compatible (Safari)"

You can find a list of useragents here:

You can specify additional search engines in Vimprobable2's config.h like so

static Searchengine searchengines[] = {
{ "b",         "" },
{ "d",         "" },
{ "g",         "" },
{ "a",         "" },
{ "w",         "" },

If you are running Vimprobable in tabbed, you can direct other applications to open webpages and have them captured in tabbed, rather than in a separate instance of Vimprobable by starting Vimprobable with an xid:

 $(tabbed -d >/tmp/tabbed.xid); vimprobable2 -e $(</tmp/tabbed.xid)

and then directing the other applications to use that xid to launch Vimprobable:

 exec vimprobable2 -e $(</tmp/tabbed.xid) "$1"

HTML5 Video

To get Vimprobable to play HTML5 Video, you will need to ensure that all of the gstreamer plugins are installed:

# pacman -S gstreamer0.10 gstreamer0.10-bad gstreamer0.10-base gstreamer0.10-base-plugins gstreamer0.10-ffmpeg gstreamer0.10-good

See this thread for details: