diff options
| author |  Dieter Plaetinck <dieter@plaetinck.be> | 2009-08-26 21:10:03 +0200 |
|---|---|---|
| committer | Dieter Plaetinck <dieter@plaetinck.be> | 2009-08-26 21:10:03 +0200 |
| commit | eccf51eb3f74a479a279d61959afa2804f1c29f6 (patch) | |
| tree | 75e6b68a7a3d47569435e8d7290a3007e0d2fcab /README | |
| parent | 9ffda40a7fe43be4df100aa1e599d4556833b4ad (diff) | |
| parent | 769f5f32d395a2c01f0ab06f29da952b3d13485e (diff) | |
Merge commit 'remotes/holizz/nouzblctrl' into experimental
Diffstat (limited to 'README')
| -rw-r--r-- | README | 7 |
1 files changed, 3 insertions, 4 deletions
@@ -44,7 +44,7 @@ Time to change that! - 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. + one can list all images on a page using the socket, 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. @@ -73,9 +73,8 @@ There are several interfaces to interact with uzbl: * 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>` + The socket is full duplex but you need a socket-compatible wrapper such as socat to work with it. + For example: echo <command> | socat - unix-connect:<socketfile> 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. |