[Surfraw-devel] user elvi directory?
Sumant Oemrawsingh
soemraws at xs4all.nl
Tue Oct 6 18:53:47 UTC 2009
On Tue, Oct 06, 2009 at 12:38:26AM +0100, James Rowe wrote:
> * Sumant Oemrawsingh (soemraws at xs4all.nl) wrote:
> > I would like to write and contribute some elvi, but would like to test them
> > first. While doing this, I realised there is no way for a user to make and
> > keep his own directory of elvi. Is this done on purpose?
> >
> > Such an option would make writing/debugging my elvi easier. Surfraw is
> > installed globally and I think it's less nice to also keep a surfraw install
> > in my home dir or to copy as root my test elvi every time.
>
> As you're sourcing the surfraw script at the top of your elvi you can
> just call them from where you're writing them to test:
>
> 0 jay at kate ~ $ cd ~
> 0 jay at kate ~ $ cp /usr/share/surfraw/urban my_test
> 0 jay at kate ~ $ ./my_test --help | head -n1
> Usage: my_test [options] [search words]...
>
> > I could dive into the code and provide such an option, if this is not
> > something people are opposed to.
>
> The idea as a general solution sounds good though, being able to dump
> all those local elvis that aren't suitable for upstream in ~/.elvi would
> probably be nice for me too. Currently, my package manager takes care
> of my local elvis in /usr, but a local directory would probably be
> easier on systems where this isn't a one-liner.
>
> Thanks,
>
> James
>
Hi James,
Thanks for your answer. You are right about writing and testing them from
running them directly. However, I'm using uzbl for browsing, and opening urls
and bookmarks is done through surfraw (if the entered text doesn't have the
appearance of a url itself). Thus it would be nice to be able to call them
from surfraw itself, while just browsing the web.
Since you support the idea of adding a ~/.elvi directory, I'd like to patch
surfraw and surfraw-update-path. So what's the approach I should take here? Do
I submit a patch to this list, or can I git push?
Thanks,
Sumant
More information about the Surfraw-devel
mailing list