edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Plugin Converters
Date: Wed, 15 Apr 2015 08:23:06 +0100	[thread overview]
Message-ID: <20150415072306.GK9150@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <20150315022022.eklhad@comcast.net>

[-- Attachment #1: Type: text/plain, Size: 1183 bytes --]

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.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2015-04-15  7:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-15  6:20 Karl Dahlke
2015-04-15  7:23 ` Adam Thompson [this message]
2015-04-15 14:24   ` Karl Dahlke
2015-04-16 19:29     ` Adam Thompson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150415072306.GK9150@toaster.adamthompson.me.uk \
    --to=arthompson1990@gmail.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=eklhad@comcast.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).