From: Dale Snell <ddsnell@frontier.com>
To: help-gnu-emacs@gnu.org
Subject: Re: w3m duckduckgo as default search engine next page
Date: Wed, 23 Oct 2013 10:55:25 -0700 [thread overview]
Message-ID: <20131023105525.14972c9d@zothique> (raw)
In-Reply-To: <87sivrx606.fsf@gmx.co.uk>
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.
--Dale
--
"Come, muse, let us sing of rats." -- James Grainger
next prev parent reply other threads:[~2013-10-23 17:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 22:43 w3m duckduckgo as default search engine next page yggdrasil
2013-10-23 1:18 ` Eric Abrahamsen
2013-10-23 17:16 ` yggdrasil
2013-10-23 17:55 ` Dale Snell [this message]
2013-10-28 23:23 ` yggdrasil
[not found] <mailman.4504.1382481855.10748.help-gnu-emacs@gnu.org>
2013-10-22 23:10 ` Emanuel Berg
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=20131023105525.14972c9d@zothique \
--to=ddsnell@frontier.com \
--cc=help-gnu-emacs@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.