lariza(1)

NAME
lariza.usage - extended usage hints

DESCRIPTION
lariza is a simple web browser using GTK+ 3, GLib and WebKit2GTK+. This manpage contains additional hints and pointers regarding its usage.

HOTKEYS

  Global hotkeys
These hotkeys work when either the location bar or the web view is being focused.

Mod1 + q
    Close the current window. Quits the entire program if this was the last window and if there are no more active downloads (download manager is shown otherwise).

Mod1 + w
    Go to your “homepage”. See the environment variable $LARIZA_HOME_URI.

Mod1 + e
    Open a new window.

Mod1 + r
    Reload the current page.

Mod1 + d
    Open the download manager.

Mod1 + l
    Focus the location bar.

Mod1 + k
    Focus the location bar and set its text to :/, allowing you to easily initiate a search.

Mod1 + 2
Mod1 + n
    Repeat the last search (forward).

Mod1 + 3
    Repeat the last search (backward).

Mod1 + c
    Reload trusted certificates.

Mod1 + a / Mod1 + s
    Select tab to the left / right.

F2 / F3
    Go backward and forward in current browser history.

  Main window — WebKit viewport focused

Escape
    Stop loading.

Middle mouse
    Open the link under the pointer in a new window.

Backward / forward (mouse keys 8 and 9)
    Same as F2 and F3.

Mod1 + Scroll up
Ctrl + Scroll up
    Increase zoom level of the current page.

Mod1 + Scroll down
Ctrl + Scroll down
    Decrase zoom level of the current page.

Mod1 + Scroll horizontally
Ctrl + Scroll horizontally
    Reset zoom to $LARIZA_ZOOM.

  Main window — location bar focused

Escape
    Reset the content of the location bar to the current URI.

Return
    Commit, i.e. begin searching or open the URI.

  Download manager

Mod1 + d
Mod1 + q
    Close the download manager. Active downloads are never aborted. However, if there are no more active downloads and no more browsing windows, then the entire program will quit.

DOWNLOAD MANAGER
Open the download manager using the appropriate hotkey. A new window listing your downloads will appear. Clicking on an item will remove it from the list and — if needed — cancel the download.

There's no file manager integration, nor does lariza delete, overwrite or resume downloads. If a file already exists, it won't be touched. Instead, the new file name will have a suffix such as .1, .2, .3, and so on.

USER-SUPPLIED JAVASCRIPT FILES
After a page has been successfully loaded, the directory ~/.config/lariza/user-scripts will be scanned and each file in it ending with .js will be run as a JavaScript file in the context of said page.

During development, you will most likely want to run lariza with $LARIZA_ENABLE_CONSOLE_TO_STDOUT enabled.

lariza comes with the following scripts:

hints.js
    Press f (open link in current window) or F (open in new window) to activate link hints. After typing the characters for one of them, press Enter to confirm. Press Escape to abort.

Those bundled scripts are automatically installed on make install. To use them, though, make sure to link them to the directory mentioned above.

WEB EXTENSIONS
On startup, WebKit checks ~/.config/lariza/web_extensions for any .so files. See this blog post (http://blogs.igalia.com/carlosgc/2013/09/10/webkit2gtk-web-process-extensions/) for further information on these extensions.

lariza comes with the following extensions:

we_adblock.so
    Generic adblock. Reads patterns from the file ~/.config/lariza/adblock. Each line can contain a regular expression. These expressions match case-insensitive and partially, i.e. .*foo.* is the same as .*FOO.* and you can use anchors like ^https?://.... Please refer to the GLib reference (https://developer.gnome.org/glib/stable/glib-regex-syntax.html) for more details. Lines starting with # are ignored.

Those bundled web extensions are automatically compiled when you run make and installed on make install. To use them, though, make sure to link them to the directory mentioned above.

TRUSTED CERTIFICATES
By default, lariza trusts whatever CAs are trusted by WebKit. If you wish to trust additional certificates, such as self-signed certificates, the first thing you should do is try to add the appropriate CAs to your system-wide store.

If you wish to add simple exceptions, you can grab the certificate and store it in the directory ~/.config/lariza/certs. The filename must be equal to the hostname:

$ echo | openssl s_client -connect foo.de:443 | openssl x509 >foo.de

This tells lariza to trust the given certificate when connecting to host foo.de.

You can reload these certificates at runtime by pressing the appropriate hotkey. Note that removed certificates will be kept in memory until you restart lariza.

Note: This is NOT equal to certificate pinning. WebKit ignores user-specified certificates if the server's certificate can be validated by any system-wide CA.

SEE ALSO
lariza(1).