* Frank Terbeck <bts@bts.grml.org> [20090602 14:08]:

[...]
> a service the user might not like. Our zshrc has >4300 lines
> already and I really think we shouldn't bloat it anymore by
> doubling features.

> There is .zshrc.local for users who want custom settings.
> And those people should use it.

> Therefore, I suggest we close this bug and tag it 'wont-fix',
> with the reasoning given above.

> Mika?

ACK

regards,
-mika-

So, about this one again.

'zsh-lookup' is still not something I'd release. I am using it
myself and it works for me, but it's not yet perfect.

About this bug:
We shouldn't add functions for every tiny bit a user might prefer,
when we are already providing the *same* functionality - just via
a service the user might not like. Our zshrc has >4300 lines
already and I really think we shouldn't bloat it anymore by
doubling features.

There is .zshrc.local for users who want custom settings.
And those people should use it.

Therefore, I suggest we close this bug and tag it 'wont-fix',
with the reasoning given above.

Mika?

Regards, Frank

* Frank Terbeck <bts@bts.grml.org> [20090401 00:06]:

> I just realized this issue is marked 'release-stopper'.
> Why's that? - Needless to say, my solution won't make the next
> release.

I often (missuse ;)) release-stopper as a way to catch our attention
for a new release (and remove the tag of course if it's not a real
release stopper then). I've removed this tag right before you sent
your mail. Thanks for mentioning. :)

regards,
-mika-

Frank Terbeck <ft@bewatermyfriend.org>:
> I just realized this issue is marked 'release-stopper'.

Ha!
That mark is gone now. So, nevermind.

I just realized this issue is marked 'release-stopper'.
Why's that? - Needless to say, my solution won't make the next
release.

Regards, Frank

Michael Prokop <bts@bts.grml.org>:
> Alexander, do you have any updates or further/up2date suggestions
> regarding this issue?

My suggestion to this is:
    http://git.bewatermyfriend.org/browse/zsh-lookup/_index.html

The only search engine backend currently is google... Well, someone
would have to step forward on that one...

I'm looking forward to get this into zsh upstream (the automatic
import-into-zsh-git-repo script might have given that away), so when
that's done, this bug could vanish in no time.

I still have to improve the docs and I want to clean up the code a
little more. The system itself works pretty damn well so far. Testers
welcome. Comments welcome. Additional backends are welcome, too
 - but expect me to thoroughly review such code. :-)

Back to the topic of this bug:

You can create aliases for backends. What I'm doing for google is, I
aliased it to 's'. So, I can do:
    % lu s whatever I want to search via google
Now, let's assume I get a backend for, say, 'scroogle', a user could
alias it to 's' and be able to search via that just like I am able to
search google. Transparently. I think that pretty much covers what
this issue is about.

Regards, Frank

Alexander, do you have any updates or further/up2date suggestions regarding 
this issue?

thx && regards,
-mika-

As Google's effort to just store everything, recently discussed on
IRC, I thought it would be nice to offer alternative search engines
within grml.
After a little bit of searching (o;, I think scroogle[1] and
ixquick[2] are quite good aproaches.

Unfortunately, for the latter, I wasn't able to find out how to get,
for example 100, search results into the first page. It's just
available by settings. Please edit, if you can figure that out.

There's a SSL version for ixquick as well. But that one requires a
self-signed certificate - kinda annoying - which contains a bad cert
- e.g. w3m's complaining. In association to that it's kind of slow.

                  ---------- Footnotes ----------

[1] http://www.scroogle.org/cgi-bin/scraper.htm

[2] http://ixquick.com/