2 readme: end-user instructions
5 Rationale. AKA "why not config files?"
6 -> unify code to configure uzbl and to accept incoming commands
7 -> no more code needed for config file parsing/handling
8 -> runtime changing of configuration
11 -> new instances (open link etc) need same config/state
13 - serialize all state structs -> some libs available, could work. but:
14 - binary format not very user friendly
15 - not that easy (C has no introspection etc)
16 - iterate over state structs and generate appropriate commands to bring an instance in this state.
19 - also useful for saving state if we need to update/shutdown/..
20 -> all of this is overkill. for now we just decided to live with the fact we pass on '--config' flags,
21 it's up to the user to tweak his setup so it works.