klaus schilling <schilling.kl...@web.de> wrote:
> Will it be possible later on to add support for bidirectional remote
> control, either by means of a second fifo or by sockets (tcp/ip or unix
> namespace) that can be accessed via socat, similar to uzbl's core
> functionality? This would allow to control vimb semi-interactively via
> shell scripts and expect.
We thought about this, but we could not thought about any real use case for
that. Uzbl is completely managed over the socket, the uzbl browser is only a
script the manage the data sent and received from the uzbl-core. But vimb
follows another approach. At the moment there is no response to send if a
command was called. Sure, some commands print something to the inputbox for
the user, but I don't think that these contents are useful to be returned to a
script.
If you have a use case for this, please let me know it.
If you want to play around with something bidirectional, you could write
vimb's output into a file and read from this.
vimb -n main > outfile &
fifo=$XDG_CONFIG_HOME/vimb/vimb-fifo-main
echo ':o http://fanglingsu.github.io/vimb/<CR>' > $fifo
# yank second element's uri into register 'a'
echo '"a;y<Tab><CR>' > $fifo
# write the register to stdout
echo ':sh! echo <C-R>a<CR>' > $fifo
# now you can read the url out of the ./outfile
I know that's a little wired, but this could be a hint how to get responses
out of vimb, even if it's not implemented.
--
Daniel
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
vimb-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vimb-users
