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.
67 That being said, this kind of minimalism is not for everyone. If you're
68 looking for more features (and a more open feature policy), then you
69 might want to check out okraits' fork:
71 https://github.com/okraits/lariza/
74 ========================
75 Using lariza with tabbed
76 ========================
78 By default, lariza automatically launches an instance of suckless'
81 You can turn this feature off (see command line arguments) or you can
82 specify a command line argument to embed lariza in an arbitrary
83 container (XEMBED). Note that lariza will also automatically embed new
84 windows in the same container.
86 When using the automatically launched tabbed instance, you can't use
87 tabbed's Ctrl + Shift + Return hotkey. This is because tabbed is
88 launched with "-d", so it knows nothing about lariza. However, lariza
89 provides its own hotkey to launch a new window which will be embedded in
90 the same instance of tabbed.
99 When the WebKit viewport is focused:
102 Close the current window.
105 Go to your "homepage". See the environment variable
112 Toggles "view source mode". This will display the web pages
113 source code. Note that the page will be reloaded (which is
114 annoying but WebKit enforces this).
117 Reload the current page.
120 Open the download manager.
123 Focus the location bar.
126 Focus the location bar and set its text to "/", allowing you
127 to easily initiate a search.
130 Repeat the last search (forward).
133 Repeat the last search (backward).
139 Open the link under the pointer in a new window.
141 Backward / forward (mouse keys 8 and 9)
144 Mod1 + Wheel up or Ctrl + Wheel up
145 Increase zoom level of the current page.
147 Mod1 + Wheel down or Ctrl + Wheel down
148 Decrase zoom level of the current page.
151 When the location bar is focused:
154 Close the current window.
157 Open the download manager.
160 Reload the current page.
163 Reset the content of the location bar to "/".
166 Reset the content of the location bar to the current URI.
169 "Commit", i.e. begin searching, do a keyword based search or
176 Close the download manager (downloads are not aborted).
179 ======================
180 Command line arguments
181 ======================
185 lariza [OPTION]... [URI]...
187 In addition to the standard arguments of GTK+ 2, lariza knows about the
191 Embeds the main window and all newly created windows in the
192 window specified by <wid>. The download manager is always a
196 Print all navigation requests on STDERR.
199 Disables cooperative instances.
202 Disables automatic launching of suckless' tabbed.
204 After these options there can be any number of URIs. If no URIs are
205 given, $LARIZA_HOME_URI will be opened.
208 =====================
209 Environment variables
210 =====================
212 In addition to the standard variables of GTK+ 2, lariza knows about the
213 following environment variables:
215 LARIZA_ACCEPTED_LANGUAGE
216 In HTTP requests, WebKit sets the "Accepted-Language" header to
217 this value. Defaults to "en-US".
220 All downloads are automatically stored in this directory.
224 Cooperative instances are implemented using a named pipe in the
225 file system. The name of this pipe usually is (at least on
226 modern systems following XDG "standards"):
228 /var/run/user/$UID/lariza.fifo-$LARIZA_FIFO_SUFFIX
230 $UID is the id of your user. $LARIZA_FIFO_SUFFIX defaults to
231 "main". If you change this variable, you can launch several
232 independent cooperative instances of lariza.
235 This URI will be opened by pressing the appropriate hotkeys
236 ("homepage" or "new window") and if no URIs are specified on the
237 command line. Defaults to "about:blank".
240 Lariza will identify itself with this string. See source code
241 for the default value.
244 Zoom level for WebKit viewports. Defaults to 1.0.
251 lariza has built-in adblock functionality. In each line of
253 ~/.config/lariza/adblock.black
255 you can store a regular expression. These expressions match
256 case-insensitive and partially, i.e. ".*foo.*" is the same as ".*FOO.*"
257 and you can use anchors like "^https?://...".
259 Lines starting with "#" are ignored.
262 =======================
263 Keyword based searching
264 =======================
266 In this file, you can configure keywords and the associated URIs:
268 ~/.config/lariza/keywordsearch
270 Each line has to look like this:
272 wi https://en.wikipedia.org/w/index.php?title=Special:Search&search=%s
274 "wi" is the keyword, so when opening "wi foo", lariza will search in
275 Wikipedia. Note the "%s" at the end of the URI: This is where your
276 search term will be placed.
278 Lines starting with "#" are ignored.
285 Open the download manager using the appropriate hotkey. A new window
286 listing your downloads will appear. Clicking on an item will remove it
287 from the list and -- if needed -- cancel the download.
289 There's no file manager integration (I don't use one), nor does lariza
290 delete, overwrite or resume downloads. If a file already exists, it
291 won't be touched. Instead, the new file name will have a suffix such as
292 ".1", ".2", ".3" and so on.
299 WebKit does create files in your $XDG_* directories, i.e. ~/.local/share
300 or ~/.cache. It's up to you what you want to do with this junk. I remove
301 it regularly when no WebKit browser is running. Another option would be
302 to change the $XDG_* variables.
304 I have explicitly not turned off the local storage feature in WebKit
305 because I don't know if this breaks web applications.
312 lariza needs the following Arch Linux packages:
315 - webkitgtk (WebKit1 API for GTK+ 3)
324 - http://webkitgtk.org/reference/webkitgtk/stable/index.html
325 - https://developer.gnome.org/gtk3/stable/index.html
326 - https://developer.gnome.org/glib/stable/index.html
328 Regular expressions supported by GRegex, you can use these in your
331 - https://developer.gnome.org/glib/stable/glib-regex-syntax.html