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
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
|
### THIS PROJECT IS NOT FOR:
* people want a browser that does everything
* people who want a browser with things like a built-in bookmark manager, address bar, forward/back buttons, ...
* people who expect something that works by default. You'll need to read configs and write/edit scripts
### TO NEW PEOPLE:
* please read the documentation in /usr/share/uzbl/docs
* invoke uzbl --help
* to get you started: uzbl --uri 'http://www.archlinux.org' --config /usr/share/uzbl/examples/configs/sampleconfig
* study the sample config, have a look at all the bindings, and note how you can call the scripts to load new url from history and the bookmarks file
* note that there is no url bar. all url editing is supposed to happen _outside_ of uzbl.
For now, you can use the `load_from_*` dmenu based scripts to pick a url or type a new one or write commands into the fifo (see /usr/share/uzbl/docs/CHECKLIST)
* If you have questions, you are likely to find answers in the FAQ or in the other documentation.
### INTRODUCTION
In my opinion, any program can only be really useful if it complies to the unix philosophy.
Web browsers are frequent violators of this principle:
* They build in way too much things into the browser, dramatically decreasing the options to do things the way you want.
* They store things in way too fancy formats (xml, rdf, sqlite, ... ) which are hard to store under version control, reuse in other scripts, ...
Time to change that!
Here are the general ideas:
* each instance of uzbl renders 1 page (eg it's a small wrapper around webkit), no tabbing, tab previews, or speed dial things.
For "multiple instances management" use your window managers, or scripts.
This way you can get something much more useful than tabbing (see rationale in docs)
* very simple, plaintext , changeable at runtime configuration
* various interfaces for (programmatic) interaction with uzbl (see below)
* customizable keyboard shortcuts in vim or emacs style (whatever user wants)
* "outsource" logic that is not browsing to external scripts under the users control:
- managing bookmarks
- loading a url from bookmarks, history,.. Editing the curent url
- control cookies
- handling of downloads, history logging, etc.
- management of cache.
- password management
- Leverage the power of utilities such as grep, awk, dmenu, zenity, wget, gnupg (password file) etc.
* listen to signals and do useful stuff when triggered.
* no ad blocking built in.
Alternatives:
- privoxy looks cool and perfectly demonstrates the unix philosphy.
- same for http://bfilter.sourceforge.net
- /etc/hosts (not very good cause you need root and it affects the whole system)
uzblctrl would need to support an option to list all images on a page, so you can easily pick the links to ads to add them to your /etc/hosts.
* vimperator/konqueror-like hyperlink following.
* password management. maybe an encrypted store that unlocks with an ssh key?
* no messing in the users $HOME or in /etc: no writing of anything unless the user (or sysadmin) asks for it.
We recommend using XDG basedir spec for separation of config, data and cache. and state should be a subdir in the config dir (not part of the spec yet) too.
### CONFIGURATION / CONTROL:
The general idea is that uzbl by default is very bare bones. you can send it commands to update settings and perform actions, through various interfaces. (TODO: some default settings)
For examples, please see the sample config(s).
There are several interfaces to interact with uzbl:
* uzbl --config <filename>: <filename> will be read line by line, and the commands in it will be executed. useful to configure uzbl at startup.
If you have a file in `$XDG_CONFIG_HOME/uzbl/config` (this expands to ~/.config/uzbl/config on most systems) it will be automatically recognized
* stdin: you can also write commands into stdin
* interactive: you can enter commands (and bind them to shortcuts, even at runtime)
By default, the behaviour is modal (vi style):
command mode: every keystroke is interpreted to run commands
insert mode: keystrokes are not interpreted so you can enter text into html forms
Press ESC/i to toggle command/insert mode
But if you don't like modal interfaces, you can set `always_insert_mode` and configure a modkey to execute the commands. (emacs style).
There is also support for "chained" commands (multiple characters long) (with backspace/esc shortcuts), and keyworded commands.
Also you can have incremental matching on commands or match after pressing return. (see sampleconfig for more info)
Also, copy paste works when typing commands:
* insert (paste X cliboard)
* shift insert (paste primary selection buffer)
* FIFO & socket file: if enabled by setting their paths through one of the above means, you can have socket and fifo files available which are very useful to programatically control uzbl (from scripts etc).
The advantage of the fifo is you can write plaintxt commands to it, but it's half duplex only (uzbl cannot send a response to you).
The socket is full duplex but you need a socket-compatible wrapper such as netcat to work with it, or uzblctrl of course,
an utitly we include with uzbl made especially for writing commnands to the socket (and at some point, it will be able to tell you the response
too): `uzblctrl -s <socketfile> -c <command>`
### COMMAND SYNTAX
TODO
### VARIABLE REPLACEMENT
Some of the variables are interpreted:
* title bar: variable replacement (long and short version, depending if statusbar is visible or not)
* user agent: variable replacement
* statusbar: variable replacement + pango markup
This means you can customize how these things appear, what's shown in them and for the statusbar you can even play with the layout.
For examples, see the example config.
For a list of possible variables, see uzbl.h
For more info about the markup format see http://library.gnome.org/devel/pango/stable/PangoMarkupFormat.html
### EXTERNAL SCRIPTS
You can use external scripts with uzbl the following ways:
* let uzbl call them. these scripts are called handlers in the uzbl config. used for handling logging history, handling a new download,..
* call them yourself from inside uzbl. you can bind keys for this. examples: add new bookmark, load new url,..
* You could also use xbindkeys or your WM config to trigger scripts if uzbl does not have focus
Have a look at the sample configs and scripts!
Handler scripts that are called by uzbl are passed the following arguments:
$1 uzbl-config-file
$2 uzbl-pid
$3 uzbl-x-window-id
$4 uzbl_fifo-filename
$5 uzbl_socket-filename
$6 current page url
$7 current page title
.. [ script specific ] (optional)
The script specific arguments are this:
* history:
$8 date of visit (Y-m-d H:i:s localtime)
* add bookmark:
none
* download:
$8 url of item to download
* cookie handler
$8 GET/PUT
$9 request address host (if current page url is www.foo.com/somepage, this could be something else then foo, eg advertising from another host)
$10 request address path
$11 cookie (only with PUT requests)
Custom, userdefined scripts (`spawn foo bar`) get first the arguments as specified in the config and then the above 7 are added at the end.
### COMMAND LINE ARGUMENTS
-u, --uri=URI Uri to load (equivalent to 'set uri = URI')
-v, --verbose Whether to print all messages or just errors.
-n, --name=NAME Name of the current instance (defaults to Xorg window id)
-c, --config=FILE Config file (this is pretty much equivalent to uzbl < FILE )
--display=DISPLAY X display to use
--help Help
### BUGS
known bugs:
* Segfaults when using zoom commands (happens when max zoom already reached?).
Please report new issues @ uzbl.org/bugs
|
