### I just installed uzbl but it doesn't do much. What now?
Uzbl includes very limited default settings (statusbar settings, but no keybinds, history/download handlers etc.)
Look at /usr/share/uzbl/docs/config.h to see the default settings.
-Neither does uzbl create a default config file on startup like some other programs do because we want to give you the freedom to place your config where you want, and to use a config or not.
Have a look in /usr/share/uzbl/examples/configs to see what you can do.
+
If you save a config as $XDG\_CONFIG\_HOME/uzbl/config it will be loaded automatically.
Running with the `--verbose` flag on a command line can also be interesting.
To get you started, try this:
variables so you can try the sample stuff directly in /usr/share/uzbl/examples.
If you like what you can do, you can copy the sample stuff into your ~ and edit to your liking.
+### Why don't you just use a reasonable config by default?
+We actually did some attempts to make uzbl "usable by default" but in the
+end we had to conclude it cannot be done because of the following reasons:
+
+ * We don't want to store anything "automagically" in the users home.
+ Some people prefer different file/directory layouts, most of just want to
+ control the files in $HOME themselves.
+ * We considered the option of having a global '/etc/uzbl' which user
+ specific ones could override but that would overcomplicate things.
+ * We adhere to the [FHS](http://www.pathname.com/fhs/) (`man hier`), so
+ `uzbl -c /usr/share/...` is not an option.
+
+So even though we would like to make uzbl more usable by default, we think
+there is no sensible way to do it. Maybe downstream packagers could provide
+a note that users could copy the examples from /usr/share/uzbl/examples into
+their homes, because really, that's all that is needed if you want it to
+just "work" without controlling how yourself. (unless you have no
+xdg variables set, in which case you should be smart enough to edit the sample
+config yourself).
+
### Where is the location bar? How do I change the URL ?
Uzbl has no location bar. All changes to the uri (editing of current uri, typing new uri, loading of uri from bookmarks/history/...) happens *outside* of uzbl.
Have a look at the sample scripts in /usr/share/uzbl/examples. Most of our examples use dmenu which is a nifty little tool to pick an item from a list of items (very
We stick to "one page per uzbl instance" because that's a simple, clean and flexible method. We believe "multiple instances management" is something that must
be handled outside of uzbl by a separate/different program. Here are some solutions:
- * many window managers can (and should) handle this by default. Xmonads tabbed layout, Wmii's stacked layout and so on.
- * you can write a custom script. The only thing you need to do is focus/maximize the instance you want,
+ * Many window managers can (and should) handle this by default. Xmonads tabbed layout, Wmii's stacked layout, fluxbox or kwin tabs and so on.
+ * Uzbl supports acting as a GtkPlug to plug into GtkSockets (Xembed) so you can embed uzbl instances in other Gtk applications.
+ This allows several implementatinos, a popular one is [uzbl_tabbed.py](http://www.uzbl.org/wiki/uzbl_tabbed)
+ * If you want highest customizablity, you need the 3rd option:
+ You can also write a custom script. The only thing you need to do is focus/maximize the instance you want,
keep the others out of sight and use tools like dmenu and wmctrl to switch instances.
This allows you to use application-specific properties (such as uzbl tag, name etc).
- For more information about this approach, see docs/multiple-instances-management
- (we'll maybe include some sample scripts in the future)
- * We might implement a GtkPlug (Xembed child) in the future. So you could abuse that.
+ For more information about this approach, see docs/multiple-instances-management.
+ (If you want to work on such script, let us know and we might include it along with the other sample scripts)
### What? No support for bookmarks/history/downloads/cookies/... ? Your project sucks!
We do not support *management* of those things, because we believe a browser should only do browsing. We are firm believers in the unix philosophy.