1 .TH bollux.conf 5 0.4.0
4 \- configuration file for
8 uses a number of environment variables that can be sourced from an external file,
10 .IR $XDG_CONFIG_HOME/bollux/bollux.conf .
11 The location can be changed at runtime by invoking
12 .BR "bollux \-c CONFIG" .
14 .SS Variables you might actually want to set
15 Here are actually useful variables that are good things to set in your
17 in order of usefulness.
20 valid values are URLs; default is ''.
27 otherwise it asks the user for where to go.
28 Setting this variable works like setting a home page.
31 valid values are directories; default is '.'.
33 The directory to attempt to save downloads in.
35 will attempt to download anything whose mimetype isn't
37 and it tries to place it in
39 If it can't open the directory, save the file,
40 or if there's another file with the same name,
42 will report the name of the temporary file it saved.
45 valid values are directories; default is '$XDG_DATA_DIR/bollux'.
49 will put its data files, such as history, cert fingerprints, etc.
52 valid values are integers; default is '5'.
54 The maximum number of redirects before
57 The default is 5 as per some RFC spec.
60 valid values are '', DEBUG or QUIET; default is ''.
66 prints debug-level messages.
68 suppresses even error-level messages.
69 I'm going to be honest,
70 the difference between the levels is somewhat arbitrary.
74 typesets text/gemini content using the
77 While it's probably possible to redefine the function in
79 the default function is pretty nice (at least in my opinion).
80 The following variables control how text/gemini content is rendered:
83 valid values are integers; default is 4.
85 The left margin for text.
86 Should be at least 3, since line-markers will be displayed in the left margin.
89 valid values are integers; default is 0.
91 The total width of the window, including
93 If set to 0, attempts to use the width of the terminal,
96 The different line-types in text/gemini documents are rendered with
98 terminal escapes (e.g., '\\e[31m').
99 The following variables should hold the values between
103 meaning valid values are anything between those that are valid terminal
107 default: 35 (fg: magenta)
109 The color of the line type as defined by text/gemini.
114 The color of the link number added by typeset_gemini.
117 default: 4 (underline)
119 The color of the link's title, or if titleless, the URL.
122 default: 36 (fg: cyan)
124 The color of the link's URL.
125 If the link doesn't have a title, this isn't used.
127 .BI C_HEADER "x where x is 1, 2, or 3"
128 The color of text/gemini headers.
129 The default for level 1 is
137 default: 0 (no formatting)
139 The color of list items.
142 default: 0 (no formatting)
144 The color of preformatted lines, as delimited by '```'.
145 .SS Variables that could be configured, but probably shouldn't be
146 These variables control deeper aspects of
149 It's possible they could be tweaked to make
151 work differently, like browsing gopher instead of gemini,
152 but that capability has not been tested.
155 valid values are port numbers (1-65535); default is '1965'.
159 tries to connect to on the server.
162 valid values are protocol names (strings); default is 'gemini'.
167 valid values are as specified in 'help read'; default is '30'.
169 The request timeout duration.
170 Specified in seconds.
173 valid values are files; default is '$BOLLUX_DATADIR/lesskey'.
175 Where to store the generated
180 valid values are files; default is '$BOLLUX_DATADIR/pagesrc'.
182 Where to store the page source of the site being visited.
183 It's not used right now by
189 .I $XDG_CONFIG_HOME/bollux/bollux.conf