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>`
+When uzbl forks a new instance (eg "open in new window") it will use the same commandline arguments (eg the same --config <file>), except --uri and--name.
+If you made changes to the configuration at runtime, these are not pased on to the child.
+
### COMMAND SYNTAX
Commands are used for creating binds, altering variables and running actions. Uzbl will read commands via standard input, named fifo pipe (if fifo_dir is set) and IPC socket (when socket_dir is set). For convenience, uzbl can also be instructed to read commands from a file on startup by using the `-c' option. Indeed, the config file is nothing more than a list of commands.
Have a look at the sample configs and scripts!
-Scripts that are called by uzbl are passed the following arguments:
+Handler scripts that are called by uzbl are passed the following arguments:
$1 uzbl-config-file
$2 uzbl-pid
$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=VERBOSE Whether to print all messages or just errors.
+ -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