unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Kevin Ryde <user42@zip.com.au>
To: Karl Fogel <kfogel@red-bean.com>
Cc: iain.dalton@gmail.com, 13882@debbugs.gnu.org,
	Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#13882: 24.2; saveplace.el limit drop least recently used
Date: Sun, 10 Mar 2013 11:57:54 +1100	[thread overview]
Message-ID: <87zjyc3wbx.fsf@blah.blah> (raw)
In-Reply-To: <87a9qe52l6.fsf@kwarm.red-bean.com> (Karl Fogel's message of "Thu, 07 Mar 2013 15:20:37 -0600")

Karl Fogel <kfogel@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?





  parent reply	other threads:[~2013-03-10  0:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-05 20:49 bug#13882: 24.2; saveplace.el limit drop least recently used Kevin Ryde
2013-03-07 15:32 ` Dmitry Gutov
2013-03-07 21:20   ` Karl Fogel
2013-03-07 22:13     ` Dmitry Gutov
2013-03-10  0:57     ` Kevin Ryde [this message]
2013-03-10 22:09       ` Karl Fogel
2013-03-11 21:23         ` Kevin Ryde
2013-03-11 22:00           ` Karl Fogel
2013-03-11 22:08             ` Ian Dalton
2013-03-12  0:43               ` Kevin Ryde
2013-03-13 18:59                 ` Karl Fogel

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=87zjyc3wbx.fsf@blah.blah \
    --to=user42@zip.com.au \
    --cc=13882@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=iain.dalton@gmail.com \
    --cc=kfogel@red-bean.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).