From: Lars Ingebrigtsen <larsi@gnus.org>
To: Boruch Baum <boruch_baum@gmx.com>
Cc: 19662@debbugs.gnu.org
Subject: bug#19662: 24.4: history bloat and navigation trouble
Date: Sun, 25 Jan 2015 13:47:48 +1100 [thread overview]
Message-ID: <87fvazvanf.fsf@building.gnus.org> (raw)
In-Reply-To: <54C26E9F.5050908@gmx.com> (Boruch Baum's message of "Fri, 23 Jan 2015 10:54:07 -0500")
Boruch Baum <boruch_baum@gmx.com> writes:
> Whenever I use the 'r' or 'l' keys in eww-mode, to eww-forward-url or
> eww-back-url in the history list, the size of the history increases.
> This seems to me to be wrong. Also, this behaviour seems to make it
> impossible (for me, at least) to traverse the entire history this way,
> unless I do so in a straight sequence (eg. all eww-back-url without ever
> using eww-forward-url).
The eww history navigation is, er, original, but it's trying to solve
the problem of "how do I get back to the page I saw just a few minutes
ago".
If you're on page A, then moves to B, then moves back to A, and then
moves to C, then getting back to B in eww is <back>, <back>. Because
that's the page you saw two pages ago.
In Firefox, if you do the same, <back> will get you to A, and then
there's no more <back>, and you can never visit B by either going back
or forward.
And it seems to me like your proposed change would have the same effect.
If anybody has a better way of registering the history (that still
wouldn't "forget" B, like Firefox does), I'm all ears.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2015-01-25 2:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 15:54 bug#19662: 24.4: history bloat and navigation trouble Boruch Baum
2015-01-25 2:47 ` Lars Ingebrigtsen [this message]
2015-01-25 7:09 ` Boruch Baum
2015-01-26 2:04 ` Lars Ingebrigtsen
2015-01-26 6:29 ` Boruch Baum
2015-01-26 6:39 ` Lars Ingebrigtsen
2016-03-17 7:20 ` Marcin Borkowski
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=87fvazvanf.fsf@building.gnus.org \
--to=larsi@gnus.org \
--cc=19662@debbugs.gnu.org \
--cc=boruch_baum@gmx.com \
/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).