From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lennart Borgman Newsgroups: gmane.emacs.devel Subject: Re: Defcustoms, how do users find them? Date: Fri, 27 Nov 2009 03:22:51 +0100 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1259288615 16038 80.91.229.12 (27 Nov 2009 02:23:35 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 27 Nov 2009 02:23:35 +0000 (UTC) Cc: Emacs-Devel devel To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 27 03:23:28 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1NDqUW-0001C7-SR for ged-emacs-devel@m.gmane.org; Fri, 27 Nov 2009 03:23:25 +0100 Original-Received: from localhost ([127.0.0.1]:35715 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NDqUW-0005Jl-BV for ged-emacs-devel@m.gmane.org; Thu, 26 Nov 2009 21:23:24 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NDqUP-0005I6-KT for emacs-devel@gnu.org; Thu, 26 Nov 2009 21:23:17 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NDqUK-0005Fb-Jv for emacs-devel@gnu.org; Thu, 26 Nov 2009 21:23:16 -0500 Original-Received: from [199.232.76.173] (port=59431 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NDqUK-0005FR-Gn for emacs-devel@gnu.org; Thu, 26 Nov 2009 21:23:12 -0500 Original-Received: from mail-yx0-f175.google.com ([209.85.210.175]:51668) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NDqUK-00035b-6L for emacs-devel@gnu.org; Thu, 26 Nov 2009 21:23:12 -0500 Original-Received: by yxe5 with SMTP id 5so1183997yxe.24 for ; Thu, 26 Nov 2009 18:23:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=xAACtya44a93wO43uHUGp0zOm3aTjwdhlkS4uDaM8zs=; b=O/KQUkBElz6WF7H8GOSQK09gxGAj1myl0x8BK1PxdEjYQhg6U5/eHOZxx9QaG3nSOg 15d6KVVZcnIsdJqhR0mL398Xia9Z8N0GrqAfh11XU/HRMZnlPOSvmHI3P8bc1vhEHTFC LK8TZF5GvHWLtlhl4JifW4658/PUPI9V6Lpyo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=TwbJEkD5Al2fulOs4dRct8FPJbptqdEc/h+cq1g3pYHJ8e8Tu2a7VtTcNgspbBmgbL JC8PyVk5utWgEVsKeWldo0HwqxOnBJoWC6JDMVX23+SsmOaX2HQmSdVh1Jchs3PqYa5v BCaWaEEdLR7CtjrWTod+SskUMxyn8A77D9PXk= Original-Received: by 10.101.176.2 with SMTP id d2mr146995anp.27.1259288591349; Thu, 26 Nov 2009 18:23:11 -0800 (PST) In-Reply-To: X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:117842 Archived-At: On Fri, Nov 27, 2009 at 3:09 AM, Stefan Monnier wrote: >>> So it ends up increasing Emacs's footprint by a bit less than >>> a megabyte. =C2=A0It's not the end of the world, but it might be worthw= hile >>> trying to avoid loading this data unless it's really needed. >> The easiest seems to be to split cus-load.el in two part and only load >> this extra part in C-h v etc. > > I think C-h v, C-h f and very common operations which most of the time > do not need this info, so I'd like to avoid eating up 1MB just for that. > >>> Of course, maybe there's a way to represent the same info >>> more compactly >> I doubt it is possible, but I do not understand all the figures. >> Does it help to erase the data again after C-h v? > > Erasing the data after use might be a way around the problem. > Note that in the form in which you currently store the data (Customize > symbol properties), it's difficult to unload it. Maybe load this data only when needed and erase them always afterwards. What is the problem with erasing the data? It is just a simple loop erasing it all, or? > If you additionally split the data (e.g. based on the first letter), > you'd end up only loading a tenth of the data at a time, which would > seem a lot more reasonable. Aren't these data only needed in custom operations? Then just loading/unloading them seems not be operations that will be very frequent. They are not more frequent than commands if flag them and erase them at command level. And a 0.1 seconds delay for certain commands that either load libraries or are meant as information commands is not very much.