unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Juri Linkov <juri@linkov.net>
Cc: Yuchen Pei <hi@ypei.me>, 50497@debbugs.gnu.org
Subject: bug#50497: [PATCH] Adding eww-{next,previous,up,top}-path.
Date: Sat, 11 Sep 2021 14:18:36 +0200	[thread overview]
Message-ID: <87czpfnw4j.fsf@gnus.org> (raw)
In-Reply-To: <878s04ijhc.fsf@mail.linkov.net> (Juri Linkov's message of "Fri,  10 Sep 2021 19:10:23 +0300")

Juri Linkov <juri@linkov.net> writes:

> Actually, the same 99.7% of all web pages doesn't provide special
> attributes "next"/"previous"/"up" used by 'n'/'p'/'u' eww commands.

That's also true, so I was sceptical about adding that (because it also
makes `C-s' etc behave sub-optimally in 99.7% of web pages), so I've
been pondering whether to remove it (or at least hide it behind and
option defaulting to "off").  But at least it has one thing going for
it -- it's a standard mechanism, not using guesswork.

> So using URL regexp matching as a fallback for other 99.7% of web pages
> that don't have numbers in URL will support (100% - 99.7%) * 2 pages.

It's true, but it'll also make `C-s' (at the end of an eww buffer) guess
at what's the next buffer, load it, and search through that instead.
Which is just kinda problematic, since an URL with a number in it isn't
necessarily related to the URL with the next number in it.

We'd be displaying web pages to the user that the user hasn't asked for,
and that the person who wrote the web site didn't intend for the user to
navigate in that way.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2021-09-11 12:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-10  3:05 bug#50497: [PATCH] Adding eww-{next,previous,up,top}-path Yuchen Pei
2021-09-10  6:43 ` Juri Linkov
2021-09-10  6:57   ` Yuchen Pei
2021-09-10 11:28 ` Lars Ingebrigtsen
2021-09-10 12:50   ` Yuchen Pei
2021-09-11 12:22     ` Lars Ingebrigtsen
2021-11-06  0:29       ` Lars Ingebrigtsen
2021-09-10 16:10   ` Juri Linkov
2021-09-11 12:18     ` Lars Ingebrigtsen [this message]
2021-09-11 19:01       ` Juri Linkov
2021-09-13  8:03         ` Lars Ingebrigtsen
2021-09-13  8:25           ` Juri Linkov
2021-09-13 17:51           ` Juri Linkov
2021-09-14 11:04             ` Lars Ingebrigtsen

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87czpfnw4j.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=50497@debbugs.gnu.org \
    --cc=hi@ypei.me \
    --cc=juri@linkov.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).