On Wed, Apr 15, 2015 at 02:20:22AM -0400, Karl Dahlke wrote:
> Plugins that convert files into text or html are now employed by the browse
> command.
> In other words, the call to /usr/bin/pdftohtml is no longer hard coded.
> Here again is my pdf block.
>
> plugin {
> type = pdf
> desc = pdf file
> suffix = pdf
> content = application/pdf
> program = pdftohtml -i -noframes %i %o >/dev/null 2>&1
> # outtype makes it a converter, h for html or t for text
> outtype = H
> }
Cool. Does the outtype work with protocol handlers as well,
and would it be possible to have a generic outtype?
I'm thinking of trying to get the following to work:
plugin {
type=scp url
protocol=scp
program=curl -s -o %o
outtype=buffer
}
Or something like that. The idea of the above plugin block is that curl is used
to download the file over scp then edbrowse loads it into the buffer.
Of course I know the same can be achieved by using the scp command (or some
script) and then loading the download into the buffer,
but I'm thinking that for some protocols it'd be nice to be able to get
edbrowse to automatically load (and possibly browse) the output.
Cheers,
Adam.
signature.asc
Description: Digital signature
_______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
