7 A simple web browser using GTK+ 2, GLib and WebKitGTK+.
12 - An input box to change the URI or to search the current page
13 - Built-in launching of suckless' tabbed
15 - Built-in download manager
16 - Optimized hotkeys: Left hand on keyboard, right hand on mouse
17 - Keyword based searching: Opening "wi foo" will search wikipedia
20 - Cooperative instances using FIFOs
21 - Support for Flash and Java
28 "lariza" stems from a german sentence:
30 Alle anderen waren mir zu anstrengend.
33 That phrase basically means: "It was too tiresome to deal with any other
34 browser." I couldn't find a simple browser that does just what I need.
35 Most of them are utterly bloated, others lack essential functions. Thus,
36 I was forced to write scripts and tools and stuff to deal with these
37 issues. That is what was tiresome. I don't want to work around bugs or
38 nonsensical behavior anymore.
40 So, I wrote my own browser^W WebKit GUI. WebKit does all the dirty work.
43 ================================
44 What lariza is and what it's not
45 ================================
47 lariza does what I need. It won't do other things. I'm open for pull
48 requests but please don't be upset if I turn them down -- which might
49 happen if it's a feature that I simply don't need.
51 Especially, it's very likely that lariza will never have a "follow
52 mode" like dwb, luakit or others have. I've used these browsers for
53 quite some time and I've also used Firefox extensions that add a "follow
54 mode". The point is, "follow mode" doesn't work anymore. This was a good
55 thing ten years ago. Today, a lot of websites make heavy use of
56 JavaScript or hovering. You NEED some kind of pointing device. I found
57 using "follow mode" to be very frustrating today, because you still have
58 to reach for the mouse all the time. So, you might as well just optimize
59 your mousing workflow.
61 lariza does not compete with powerful browsers like dwb or luakit, nor
62 with monstrous applications like Firefox or Chromium. lariza won't have
63 persistent storage, nor a plugin system, nor cloud sync, nor bookmarks.
65 lariza tries not to exceed 1000 lines of code.
68 ========================
69 Using lariza with tabbed
70 ========================
72 By default, lariza automatically launches an instance of suckless'
75 You can turn this feature off (see command line arguments) or you can
76 specify a command line argument to embed lariza in an arbitrary
77 container (XEMBED). Note that lariza will also automatically embed new
78 windows in the same container.
80 When using the automatically launched tabbed instance, you can't use
81 tabbed's Ctrl + Shift + Return hotkey. This is because tabbed is
82 launched with "-d", so it knows nothing about lariza. However, lariza
83 provides its own hotkey to launch a new window which will be embedded in
84 the same instance of tabbed.
93 When the WebKit viewport is focused:
96 Close the current window.
99 Go to your "homepage" which is the first URI specified on
106 Toggles "view source mode". This will display the web pages
107 source code. Note that the page will be reloaded (which is
108 annoying but WebKit enforces this).
111 Reload the current page.
114 Open the download manager.
117 Focus the location bar.
120 Focus the location bar and set its text to "/", allowing you
121 to easily initiate a search.
124 Repeat the last search (forward).
127 Repeat the last search (backward).
133 Open the link under the pointer in a new window.
135 Backward / forward (mouse keys 8 and 9)
138 Mod1 + Wheel up or Ctrl + Wheel up
139 Increase zoom level of the current page.
141 Mod1 + Wheel down or Ctrl + Wheel down
142 Decrase zoom level of the current page.
145 When the location bar is focused:
148 Close the current window.
151 Open the download manager.
154 Reload the current page.
157 Reset the content of the location bar to "/".
160 Reset the content of the location bar to the current URI.
163 "Commit", i.e. begin searching, do a keyword based search or
170 Close the download manager (downloads are not aborted).
173 ======================
174 Command line arguments
175 ======================
179 lariza [OPTION]... [URI]...
181 In addition to the standard arguments of GTK+ 2, lariza knows about the
185 Embeds the main window and all newly created windows in the
186 window specified by <wid>. The download manager is always a
190 Print all navigation requests on STDERR.
193 Disables cooperative instances.
196 Disables automatic launching of suckless' tabbed.
198 After these options there can be any number of URIs. If no URIs are
199 given, about:blank will be opened.
202 =====================
203 Environment variables
204 =====================
206 In addition to the standard variables of GTK+ 2, lariza knows about the
207 following environment variables:
209 LARIZA_ACCEPTED_LANGUAGE
210 In HTTP requests, WebKit sets the "Accepted-Language" header to
211 this value. Defaults to "en-US".
214 All downloads are automatically stored in this directory.
218 Cooperative instances are implemented using a named pipe in the
219 file system. The name of this pipe usually is (at least on
220 modern systems following XDG "standards"):
222 /var/run/$UID/lariza.fifo-$LARIZA_FIFO_SUFFIX
224 $UID is the id of your user. $LARIZA_FIFO_SUFFIX defaults to
225 "main". If you change this variable, you can launch several
226 independent cooperative instances of lariza.
229 Zoom level for WebKit viewports. Defaults to 1.0.
236 lariza has built-in adblock functionality. In each line of
238 ~/.config/lariza/adblock.black
240 you can store a regular expression. These expressions match
241 case-insensitive and partially, i.e. ".*foo.*" is the same as ".*FOO.*"
242 and you can use anchors like "^https?://...".
244 Lines starting with "#" are ignored.
247 =======================
248 Keyword based searching
249 =======================
251 In this file, you can configure keywords and the associated URIs:
253 ~/.config/lariza/keywordsearch
255 Each line has to look like this:
257 wi https://en.wikipedia.org/w/index.php?title=Special:Search&search=%s
259 "wi" is the keyword, so when opening "wi foo", lariza will search in
260 Wikipedia. Note the "%s" at the end of the URI: This is where your
261 search term will be placed.
263 Lines starting with "#" are ignored.
270 Open the download manager using the appropriate hotkey. A new window
271 listing your downloads will appear. Clicking on an item will remove it
272 from the list and -- if needed -- cancel the download.
274 There's no file manager integration (I don't use one), nor does lariza
275 delete, overwrite or resume downloads. If a file already exists, it
276 won't be touched. Instead, the new file name will have a suffix such as
277 ".1", ".2", ".3" and so on.
284 WebKit does create files in your $XDG_* directories, i.e. ~/.local/share
285 or ~/.cache. It's up to you what you want to do with this junk. I remove
286 it regularly if no WebKit browser is running. Another option would be to
287 change the $XDG_* variables.
289 I have explicitly not turned off the local storage feature in WebKit
290 because I don't know if this breaks web applications.
297 lariza needs the following Arch Linux packages:
309 - http://webkitgtk.org/reference/webkitgtk/stable/index.html
310 - https://developer.gnome.org/gtk2/stable/index.html
311 - https://developer.gnome.org/glib/stable/index.html
313 Regular expressions supported by GRegex, you can use these in your
316 - https://developer.gnome.org/glib/stable/glib-regex-syntax.html