From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: Occur stack Date: Thu, 16 Jan 2014 11:36:25 +0100 Organization: Organization?!? Message-ID: <87r4882oye.fsf@fencepost.gnu.org> References: <8738kq5xo5.fsf@yahoo.fr> <87ob3d645m.fsf@mail.jurta.org> <87a9ex8vi8.fsf@fencepost.gnu.org> <87eh49cfa8.fsf@mail.jurta.org> <874n5448aa.fsf@fencepost.gnu.org> <87lhygi7ja.fsf@building.gnus.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1389868611 20205 80.91.229.3 (16 Jan 2014 10:36:51 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 16 Jan 2014 10:36:51 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jan 16 11:36:57 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1W3kJl-00015F-Jp for ged-emacs-devel@m.gmane.org; Thu, 16 Jan 2014 11:36:57 +0100 Original-Received: from localhost ([::1]:59701 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W3kJl-0008Gc-7R for ged-emacs-devel@m.gmane.org; Thu, 16 Jan 2014 05:36:57 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:42948) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W3kJd-0008FN-1t for emacs-devel@gnu.org; Thu, 16 Jan 2014 05:36:54 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W3kJV-0003gq-N9 for emacs-devel@gnu.org; Thu, 16 Jan 2014 05:36:48 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:44527) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W3kJV-0003gi-Fj for emacs-devel@gnu.org; Thu, 16 Jan 2014 05:36:41 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1W3kJS-0000dC-Qn for emacs-devel@gnu.org; Thu, 16 Jan 2014 11:36:38 +0100 Original-Received: from x2f4f877.dyn.telefonica.de ([2.244.248.119]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 16 Jan 2014 11:36:38 +0100 Original-Received: from dak by x2f4f877.dyn.telefonica.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 16 Jan 2014 11:36:38 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 26 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: x2f4f877.dyn.telefonica.de X-Face: 2FEFf>]>q>2iw=B6, xrUubRI>pR&Ml9=ao@P@i)L:\urd*t9M~y1^:+Y]'C0~{mAl`oQuAl \!3KEIp?*w`|bL5qr,H)LFO6Q=qx~iH4DN; i"; /yuIsqbLLCh/!U#X[S~(5eZ41to5f%E@'ELIi$t^ Vc\LWP@J5p^rst0+('>Er0=^1{]M9!p?&:\z]|;&=NP3AhB!B_bi^]Pfkw User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) Cancel-Lock: sha1:n/yfHTFyJ7BjA8fy66CpKCsV1rY= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:168522 Archived-At: Lars Ingebrigtsen writes: > David Kastrup 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