From: Boruch Baum <boruch_baum@gmx.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 19662@debbugs.gnu.org
Subject: bug#19662: 24.4: history bloat and navigation trouble
Date: Mon, 26 Jan 2015 01:29:36 -0500 [thread overview]
Message-ID: <54C5DED0.505@gmx.com> (raw)
In-Reply-To: <87mw56i9ga.fsf@building.gnus.org>
[-- Attachment #1: Type: text/plain, Size: 1351 bytes --]
On 01/25/2015 09:04 PM, Lars Ingebrigtsen wrote:
> Boruch Baum <boruch_baum@gmx.com> writes:
>
>> No. What ends up happening is that the sequence of the history list is
>> preserved, so you can always go back to B. It has the advantage of
>> reducing bloat, and if one scrolls through history much, that bloat can
>> be great.
>>
>> I can see two uses for a history:
>> 1] a log of the sequence in which pages were visited;
>> 2] a list of visited places, in original sequence order.
>>
>> For me, #2 is far and away more useful.
>
> The current history implementation also preserves the point position,
> which is probably different in each frame. Which may or may not be
> helpful.
>
> I agree that the current way of recording the history may be overkill,
> but I've also found it very handy because it's so predictable. <back>
> <back> always, without fail, takes you back to the page you were at two
> commands ago, no matter what the command was...
>
>> One problem with the current eww implementation is that once one does
>> something like A B C D C B, it becomes difficult to get to E using
>> commands l/r
>
> Where is E in that sequence of pages?
>
That's kind of the point, it would have been historically before D.
--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-01-26 6:29 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
2015-01-25 7:09 ` Boruch Baum
2015-01-26 2:04 ` Lars Ingebrigtsen
2015-01-26 6:29 ` Boruch Baum [this message]
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=54C5DED0.505@gmx.com \
--to=boruch_baum@gmx.com \
--cc=19662@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).