[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Occur stack
From: |
Tom |
Subject: |
Re: Occur stack |
Date: |
Fri, 17 Jan 2014 13:24:31 +0000 (UTC) |
User-agent: |
Loom/3.14 (http://gmane.org/) |
Andreas Röhler <andreas.roehler <at> online.de> writes:
>
> In cases where a plenty of occur-calls is done, maybe
> the discussion WRT to memory pertains?
The aim of this little experimental code is only to demonstrate
how this feature could work, not to be an optimal implementation.
But it only stores the last 10 occur buffers, so memory may not
be a real concern (most occur buffers are not huge in
my experience) and if the user uses occur frequently then
every buffer is pushed out of this stored history after a while
and the garbage collector can do its job.
- Re: Occur stack, (continued)
- Re: Occur stack, Lars Ingebrigtsen, 2014/01/16
- Re: Occur stack, David Kastrup, 2014/01/16
- Re: Occur stack, Stefan Monnier, 2014/01/16
- Re: Occur stack, David Kastrup, 2014/01/16
- Re: Occur stack, Lars Ingebrigtsen, 2014/01/17
- Re: Occur stack, Tom, 2014/01/14
Re: Occur stack, Andreas Röhler, 2014/01/15
Re: Occur stack, Tom, 2014/01/17
Re: Occur stack, Tom, 2014/01/18
Re: Occur stack, Stefan Monnier, 2014/01/18
Re: Occur stack, Tom, 2014/01/19
Re: Occur stack, Daniel Colascione, 2014/01/19
Re: Occur stack, Stefan Monnier, 2014/01/19
Re: Occur stack, Tom, 2014/01/19
Re: Occur stack, Lars Ingebrigtsen, 2014/01/18