Features:
- A WebKit viewport
- - An input box to change the URL or to search the current page
+ - An input box to change the URI or to search the current page
- Built-in launching of suckless' tabbed
- Built-in adblock
- Built-in download manager
Close the current window.
Mod1 + w
- Go to your "homepage" which is the first URL specified on
+ Go to your "homepage" which is the first URI specified on
the command line.
Mod1 + e
Reset the content of the location bar to "/".
Escape
- Reset the content of the location bar to the current URL.
+ Reset the content of the location bar to the current URI.
Return
"Commit", i.e. begin searching, do a keyword based search or
- open the URL.
+ open the URI.
Download manager
- Mod1 + q
+ Mod1 + d
Close the download manager (downloads are not aborted).
Command line arguments
======================
+Usage:
+
+ lariza [OPTION]... [URI]...
+
In addition to the standard arguments of GTK+ 2, lariza knows about the
following options:
-T
Disables automatic launching of suckless' tabbed.
+After these options there can be any number of URIs. If no URIs are
+given, about:blank will be opened.
+
=====================
Environment variables
file system. The name of this pipe usually is (at least on
modern systems following XDG "standards"):
- /var/run/$UID/lariza.fifo-$LARIZA_FIFO_SUFFIX
+ /var/run/user/$UID/lariza.fifo-$LARIZA_FIFO_SUFFIX
$UID is the id of your user. $LARIZA_FIFO_SUFFIX defaults to
"main". If you change this variable, you can launch several
Keyword based searching
=======================
-In this file, you can configure keywords and the associated URLs:
+In this file, you can configure keywords and the associated URIs:
~/.config/lariza/keywordsearch
wi https://en.wikipedia.org/w/index.php?title=Special:Search&search=%s
"wi" is the keyword, so when opening "wi foo", lariza will search in
-Wikipedia. Note the "%s" at the end of the URL: This is where your
+Wikipedia. Note the "%s" at the end of the URI: This is where your
search term will be placed.
Lines starting with "#" are ignored.
WebKit does create files in your $XDG_* directories, i.e. ~/.local/share
or ~/.cache. It's up to you what you want to do with this junk. I remove
-it regularly if no WebKit browser is running. Another option would be to
-change the $XDG_* variables.
+it regularly when no WebKit browser is running. Another option would be
+to change the $XDG_* variables.
I have explicitly not turned off the local storage feature in WebKit
because I don't know if this breaks web applications.