unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: Occur stack
Date: Thu, 16 Jan 2014 11:36:25 +0100	[thread overview]
Message-ID: <87r4882oye.fsf@fencepost.gnu.org> (raw)
In-Reply-To: 87lhygi7ja.fsf@building.gnus.org

Lars Ingebrigtsen <larsi@gnus.org> writes:

> David Kastrup <dak@gnu.org> writes:
>
>> My point, namely that an easibly accessible history regenerated
>> transparently is much cheaper than buffers to keep around.
>
> I doubt that's correct.  Putting the text of the buffer into a string
> (and recovering it) when you hit `l' is much cheaper than running
> "grep".
>
> There will be an increased memory usage, of course, but we can limit the
> history depth to something reasonable.

You are aware that you are in agreement with me?  The increased memory
usage is _exactly_ why one would have to limit the history depth "to
something reasonable".

I see no actual point moving the history into strings from buffers and
back again: easier to just keep the buffers.  Also much more transparent
to reclaim memory if you run out of it: you can find and delete large
buffers, but you won't easily figure out that some history string is
eating all your memory.

-- 
David Kastrup




  reply	other threads:[~2014-01-16 10:36 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14 16:24 Occur stack Tom
2014-01-14 16:35 ` Nicolas Richard
2014-01-14 16:57   ` Tom
2014-01-14 17:00     ` Tom
2014-01-14 17:07     ` Juanma Barranquero
2014-01-14 17:12       ` Tom
2014-01-14 17:21         ` Lars Magne Ingebrigtsen
2014-01-14 20:30           ` Tom
2014-01-14 20:40             ` Tom
2014-01-14 21:08           ` Daniel Colascione
2014-01-14 21:24             ` John Yates
2014-01-14 21:32             ` Drew Adams
2014-01-14 21:26           ` Stefan Monnier
2014-01-14 17:41         ` Allen S. Rout
2014-01-15  8:27       ` Juri Linkov
2014-01-15  9:06         ` David Kastrup
2014-01-16  7:57           ` Juri Linkov
2014-01-16  8:53             ` David Kastrup
2014-01-16  9:46               ` Lars Ingebrigtsen
2014-01-16 10:36                 ` David Kastrup [this message]
2014-01-16 13:47                   ` Stefan Monnier
2014-01-16 13:54                     ` David Kastrup
2014-01-17 15:52                       ` Lars Ingebrigtsen
2014-01-15 18:52 ` Andreas Röhler
2014-01-15 20:16   ` Tom
2014-01-16 17:19     ` Tom
2014-01-17  8:24       ` Andreas Röhler
2014-01-17 13:24         ` Tom
2014-01-19 14:50           ` Andreas Röhler
2014-01-19 16:03             ` Tom
2014-01-17 17:19         ` Tom
2014-01-18 17:01           ` Tom
2014-01-19  2:39             ` Stefan Monnier
2014-01-19  6:40               ` Tom
2014-01-19  7:12                 ` Daniel Colascione
2014-01-19 14:38                 ` Stefan Monnier
2014-01-19 15:56                   ` Tom
2014-01-18 17:04           ` Lars Ingebrigtsen
2014-01-19  2:45             ` Stefan Monnier
2014-01-21  7:51               ` Juri Linkov
2014-01-21  9:05                 ` joakim
2014-01-22  8:03                   ` Juri Linkov
2014-01-21 19:42               ` Lars Ingebrigtsen
2014-01-22  1:27                 ` Stefan Monnier

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=87r4882oye.fsf@fencepost.gnu.org \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.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).