From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier <monnier@iro.umontreal.ca> Newsgroups: gmane.emacs.bugs Subject: bug#5529: `uniquify-buffer-name-style' doesn't exist Date: Sun, 07 Feb 2010 20:49:27 -0500 Message-ID: <jwv3a1c33kp.fsf-monnier+emacs@gnu.org> References: <20100205151859.GA7866@muc.de> <e01d8a51002050756v21f49824xaeb9cc5ba8ef048e@mail.gmail.com> <20100205181742.GB7866@muc.de> <e01d8a51002051018p3aeafadcoa428dcc405a2e407@mail.gmail.com> <20100206181748.GB2157@muc.de> <e01d8a51002061018n31bc98a4lb8bbf06d90f71f4@mail.gmail.com> <20100206204400.GC2157@muc.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1265593959 11264 80.91.229.12 (8 Feb 2010 01:52:39 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 8 Feb 2010 01:52:39 +0000 (UTC) Cc: 5529@debbugs.gnu.org To: Alan Mackenzie <acm@muc.de> Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Feb 08 02:52:36 2010 Return-path: <bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org> Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from <bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org>) id 1NeInj-0001V1-Gd for geb-bug-gnu-emacs@m.gmane.org; Mon, 08 Feb 2010 02:52:35 +0100 Original-Received: from localhost ([127.0.0.1]:46609 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NeInj-0000MA-3N for geb-bug-gnu-emacs@m.gmane.org; Sun, 07 Feb 2010 20:52:35 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NeInW-0000Ic-0U for bug-gnu-emacs@gnu.org; Sun, 07 Feb 2010 20:52:22 -0500 Original-Received: from [199.232.76.173] (port=49445 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NeInV-0000IA-0H for bug-gnu-emacs@gnu.org; Sun, 07 Feb 2010 20:52:21 -0500 Original-Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1NeInT-0000oP-2b for bug-gnu-emacs@gnu.org; Sun, 07 Feb 2010 20:52:20 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:39463) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1NeInS-0000o9-NG for bug-gnu-emacs@gnu.org; Sun, 07 Feb 2010 20:52:18 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.69) (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1NeIlG-0006nv-SV; Sun, 07 Feb 2010 20:50:02 -0500 X-Loop: bug-gnu-emacs@gnu.org Resent-From: Stefan Monnier <monnier@iro.umontreal.ca> Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-To: owner@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 08 Feb 2010 01:50:02 +0000 Resent-Message-ID: <handler.5529.B5529.126559377326141@debbugs.gnu.org> Resent-Sender: bug-gnu-emacs@gnu.org X-Emacs-PR-Message: followup 5529 X-Emacs-PR-Package: emacs X-Emacs-PR-Keywords: Original-Received: via spool by 5529-submit@debbugs.gnu.org id=B5529.126559377326141 (code B ref 5529); Mon, 08 Feb 2010 01:50:02 +0000 Original-Received: (at 5529) by debbugs.gnu.org; 8 Feb 2010 01:49:33 +0000 Original-Received: from localhost ([127.0.0.1] helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.69) (envelope-from <debbugs-submit-bounces@debbugs.gnu.org>) id 1NeIkn-0006na-1g for submit@debbugs.gnu.org; Sun, 07 Feb 2010 20:49:33 -0500 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.183] helo=ironport2-out.pppoe.ca) by debbugs.gnu.org with esmtp (Exim 4.69) (envelope-from <monnier@iro.umontreal.ca>) id 1NeIkl-0006nV-IP for 5529@debbugs.gnu.org; Sun, 07 Feb 2010 20:49:31 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AuAEAJf8bktLd+Rw/2dsb2JhbACBMtUihFQEim8 X-IronPort-AV: E=Sophos;i="4.49,424,1262581200"; d="scan'208";a="55513229" Original-Received: from 75-119-228-112.dsl.teksavvy.com (HELO pastel.home) ([75.119.228.112]) by ironport2-out.pppoe.ca with ESMTP; 07 Feb 2010 20:49:27 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id 8CDA37F5D; Sun, 7 Feb 2010 20:49:27 -0500 (EST) In-Reply-To: <20100206204400.GC2157@muc.de> (Alan Mackenzie's message of "Sat, 6 Feb 2010 20:44:00 +0000") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.91 (gnu/linux) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.11 Precedence: list Resent-Date: Sun, 07 Feb 2010 20:50:02 -0500 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs.gnu.org> List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/bug-gnu-emacs>, <mailto:bug-gnu-emacs-request@gnu.org?subject=unsubscribe> List-Archive: <http://lists.gnu.org/pipermail/bug-gnu-emacs> List-Post: <mailto:bug-gnu-emacs@gnu.org> List-Help: <mailto:bug-gnu-emacs-request@gnu.org?subject=help> List-Subscribe: <http://lists.gnu.org/mailman/listinfo/bug-gnu-emacs>, <mailto:bug-gnu-emacs-request@gnu.org?subject=subscribe> Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:34949 Archived-At: <http://permalink.gmane.org/gmane.emacs.bugs/34949> >> > Seems to me that what's wanted is an autoload for variables, just like >> > we've got for functions/macros. =A0Or have we got this already? =A0The= n when >> > anybody tries to access this variable in any way, uniquify.elc would g= et >> > loaded. >> We can autoload defcustoms, but there are so many so we probably do >> not want that. > Why? The "eight megabytes and continually swapping" joke is several > decades out of date. Actually, the problem is not just its size, it's that the current ;;;###autoload behavior for variables is not quite as clean as it is for functions: it doesn't auto-load the package when accessing the var, but instead it preloads just the variable, thus changing the order of execution between the variable that are "autoloaded" and those that aren't, thus leading to all kinds of bugs and problems. What Lennart has been working on is a real autoloading mechanism, whereby the package will be loaded when the user asks to customize this variable. >> Therefore Stefan instead had the idea that we can make them available >> for completion, for example when you do "M-x customize-option". If >> choosen they will then be loaded. I started to work a bit on that, but >> it is not finished. (See the thread I pointed to.) > What does "make them available" mean? Create a separate obarray for > them, perhaps? The technical means by which the autoloading will take place is not finalized yet. Lennart has something implemented using some technique, but IIRC it was still using too much memory for my taste. Stefan