blob: 1d4bb04bafad0c2a7288392c7b8e8e35afe32ac8 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
|
.TH lariza 1 "2020-03-11" "lariza" "User Commands"
.\" --------------------------------------------------------------------
.SH NAME
lariza \- simple web browser
.\" --------------------------------------------------------------------
.SH SYNOPSIS
\fBlariza\fP
[\fB\-e\fP \fIwid\fP]
[\fB\-C\fP]
[\fB\-T\fP]
[\fIURI ...\fP]
.\" --------------------------------------------------------------------
.SH DESCRIPTION
\fBlariza\fP is a simple web browser using GTK+ 3, GLib and WebKit2GTK+.
.\" --------------------------------------------------------------------
.SH OPTIONS
In addition to the standard arguments of GTK+ 3, \fBlariza\fP knows
about the following options:
.TP
\fB\-e\fP \fIwid\fP
Embeds the main window and all newly created windows in the window
specified by \fIwid\fP. The download manager is always a \(lqpopup\(rq.
.TP
\fB\-C\fP
Disables cooperative instances.
.TP
\fB\-T\fP
Disables automatic launching of suckless' \fBtabbed\fP(1).
.P
After these options there can be any number of URIs. If no URIs are
given, $\fBLARIZA_HOME_URI\fP will be opened.
.\" --------------------------------------------------------------------
.SH ENVIRONMENT
In addition to the standard variables of GTK+ 3, \fBlariza\fP knows
about the following environment variables:
.P
.TP
\fBLARIZA_ACCEPTED_LANGUAGE\fP
In HTTP requests, WebKit sets the \(lqAccepted-Language\(rq header to
this value. Defaults to \fBen-US\fP.
.TP
\fBLARIZA_DOWNLOAD_DIR\fP
All downloads are automatically stored in this directory. If you want to
stick to XDG directories, then you should configure your
\(lqxdg-user-dirs\(rq and use this:
\f(CW
.nf
\&LARIZA_DOWNLOAD_DIR=$(xdg-user-dir DOWNLOAD)
.fi
\fP
This variable defaults to \fB/var/tmp\fP.
.TP
\fBLARIZA_ENABLE_CONSOLE_TO_STDOUT\fP
Enable writing WebKit console messages to stdout.
.TP
\fBLARIZA_FIFO_SUFFIX\fP
Cooperative instances are implemented using a named pipe in the file
system. The name of this pipe usually is (at least on modern systems
following XDG \(lqstandards\(rq):
\fI/var\:/run\:/user\:/$UID\:/lariza.fifo\:-$LARIZA_FIFO_SUFFIX\fP.
$\fBUID\fP is the id of your user. $\fBLARIZA_FIFO_SUFFIX\fP defaults to
\fBmain\fP. If you change this variable, you can launch several
independent cooperative instances of \fBlariza\fP.
.TP
\fBLARIZA_HISTORY_FILE\fP
If set, \fBlariza\fP will write each visited URI to that file. This path
can point to a named pipe, but be aware that the browser will block
until a reader at the other end of the pipe has read all pending data.
.TP
\fBLARIZA_HOME_URI\fP
This URI will be opened by pressing the appropriate hotkeys
(\(lqhomepage\(rq or \(lqnew window\(rq) and if no URIs are specified on
the command line. Defaults to \fBabout:blank\fP.
.TP
\fBLARIZA_USER_AGENT\fP
\fBlariza\fP will identify itself with this string. Uses WebKit's
default value if unset.
.TP
\fBLARIZA_ZOOM
Zoom level for WebKit viewports. Defaults to \fB1.0\fP.
.\" --------------------------------------------------------------------
.SH FILES
XDG variables will be used to construct these paths.
.TP
\fI~/.config\:/lariza\:/adblock.black\fP
Adblock patterns. See \fBlariza.usage\fP(1).
.TP
\fI~/.config\:/lariza\:/certs\fP
Directory where trusted certificates are stored. See
\fBlariza.usage\fP(1).
.TP
\fI~/.config\:/lariza\:/keywordsearch\fP
Configuration file for keyword base searching. See
\fBlariza.usage\fP(1).
.TP
\fI~/.config\:/lariza\:/scripts\fP
Directory to store user-supplied JavaScript snippets. See
\fBlariza.usage\fP(1).
.TP
\fI~/.local\:/share\:/lariza\:/web_extensions\fP
Sets the directory where WebKit will look for web extensions. See
\fBlariza.usage\fP(1).
.P
The executable \fIlariza-external-handler\fP must be located somewhere
in your $\fBPATH\fP, if you want to make use of the external URI
handler. See \fBlariza.usage\fP(1) for details.
.\" --------------------------------------------------------------------
.SH LICENSE
\fBlariza\fP is released under the MIT license. See the accompanying
\fILICENSE\fP file.
.\" --------------------------------------------------------------------
.SH HISTORY
\fBlariza\fP was originally written by Peter Hofmann. The project
was started in June 2014.
.\" --------------------------------------------------------------------
.SH "SEE ALSO"
.BR lariza.usage (1),
.BR tabbed (1).
|
