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: Tue, 12 Mar 2013 08:23:52 +1100 [thread overview]
Message-ID: <87y5dt8wbb.fsf@blah.blah> (raw)
In-Reply-To: <87li9udi0o.fsf@floss.red-bean.com> (Karl Fogel's message of "Sun, 10 Mar 2013 17:09:11 -0500")
Karl Fogel <kfogel@red-bean.com> writes:
>
> or that in the abstract one would be
> tempted to do that?
Yes, in the abstract :-).
> I'm happy to address a concrete proposal,
I would say take away the `sort', and don't have an option for it.
> How would the user hook in to run the sort, unless we provide some
> option in saveplace.el?
I presume a user has two .emacs-places files and wants to merge them.
Was that the motivation for the sort?
If yes then I would say the files can be sorted easily enough at that
time, no need to always save sorted. In fact I would say keeping
most-recent-first order might be desirable when merging two files
anyway.
> I'm just having
> trouble understanding exactly what you're saying above.
The second part I wondered what happens if I have two running copies of
emacs, both with save-place enabled. When the first one exits it writes
.emacs-places. When the second one exits it too writes .emacs-places.
I suspect the second overwrites the first. Was such a situation the
motivation for the sort to "merge"?
next prev parent reply other threads:[~2013-03-11 21:23 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
2013-03-10 22:09 ` Karl Fogel
2013-03-11 21:23 ` Kevin Ryde [this message]
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=87y5dt8wbb.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).