From: Yuchen Pei <hi@ypei.me>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 50497@debbugs.gnu.org
Subject: bug#50497: [PATCH] Adding eww-{next,previous,up,top}-path.
Date: Fri, 10 Sep 2021 22:50:45 +1000 [thread overview]
Message-ID: <87v938wq56.fsf@ypei.me> (raw)
In-Reply-To: <87ee9wpt38.fsf@gnus.org>
[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Yuchen Pei <hi@ypei.me> writes:
>
>> I often find myself wanting to navigate paginated web pages
>> (e.g. <https://media.libreplanet.org/videos?page=4>), or to go
>> up or
>> all the way up when visiting a web page, which is why I added
>> these
>> functions to my eww.
>>
>> Does this change make sense? If so I will amend the patch to
>> include
>> tests, doc and bug number.
>
> I'm not sure this is general enough to include in eww -- these
> are
> commands that will fail in 99.7% of all web pages, because they
> don't
> have URLs that are structured this way.
OK, how about having them as a fallback to
eww-{nex,previous,up,top}-url, as Juri mentioned? From my
experience these -url functions don't work for most web pages
either, so adding my functions as a fallback would increase the
chance that the keys will work in some meaningful way.
--
Best,
Yuchen
PGP Key: 47F9 D050 1E11 8879 9040 4941 2126 7E93 EF86 DFD0
<https://ypei.me/assets/ypei-pubkey.txt>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 243 bytes --]
next prev parent reply other threads:[~2021-09-10 12:50 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 [this message]
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
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=87v938wq56.fsf@ypei.me \
--to=hi@ypei.me \
--cc=50497@debbugs.gnu.org \
--cc=larsi@gnus.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 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).