Re: w3m duckduckgo as default search engine next page

[yggdrasil]

Dale Snell <ddsnell@frontier.com> writes:

> On Wed, 23 Oct 2013 18:16:09 +0100
> <yggdrasil@gmx.co.uk> wrote:
>
>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>> 
>> > That's not a w3m thing, that's provided by the web page in question.
>> > Google provides nice rel="next|prev" links, and SPC in w3m is bound to a
>> > command that will scroll the buffer, or follow a "next" link if you're
>> > at the bottom of the buffer and there is such a link.
>> >
>> > If the site doesn't provide next/prev, there's not much w3m can do, at
>> > least not out of the box.
>> 
>> Yeah, I figured as much, sorry for being unclear. I am not trying to
>> insinuate a bug in w3m when it seems to be rather poor web design
>> practice (if there is a convention that is, which seems a reasonable
>> assumption...) here, but was rather hoping there's 1) an easy way to
>> tweak w3m to overcome this limitation in the web page, or 2) another
>> search engine to use that has these links, which is not google. 
>
> You might want to look into Startpage, <https://startpage.com>.
> That engine has Prev/Next links at the bottom of its search
> pages, so might work correctly with w3m.
>

Thanks, never heard about this before but it looks like a great
option. I'll take it! 

/J