GNU bug report logs - #13882
24.2; saveplace.el limit drop least recently used

Previous Next

Package: emacs;

Reported by: Kevin Ryde <user42 <at> zip.com.au>

Date: Tue, 5 Mar 2013 20:52:01 UTC

Severity: normal

Tags: patch

Found in version 24.2

Done: Karl Fogel <kfogel <at> red-bean.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Kevin Ryde <user42 <at> zip.com.au>
To: Karl Fogel <kfogel <at> red-bean.com>
Cc: iain.dalton <at> gmail.com, 13882 <at> debbugs.gnu.org, Dmitry Gutov <dgutov <at> yandex.ru>
Subject: bug#13882: 24.2; saveplace.el limit drop least recently used
Date: Sun, 10 Mar 2013 11:57:54 +1100
Karl Fogel <kfogel <at> red-bean.com> writes:
>
> However, I think the answer to that is also clear: unsorted should be
> the default (or rather, chronologically sorted should be the default),
> and if a user wants the list alphabetized (for merge purposes), they can
> configure it so.

You'd be very tempted to let them put it through the sort program or
sort func themselves, not have any option at all.

In a merge you presumably still want the most-recent 400 visits, or
whatever limit, which would require per-entry timestamps to do properly.
And if you're not limiting it then I imagine there's no need to sort,
just concat the lot.

I wondered how well the simple save-place-loaded bit works when you've
got two running copies of emacs.  I suppose the save places of the last
one to exit will overwrite anything the others saved.  That wasn't the
aim of the "merge" was it?




This bug report was last modified 12 years and 75 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.