From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juanma Barranquero Newsgroups: gmane.emacs.devel Subject: Re: A few questions about desktop.el Date: Tue, 9 Aug 2005 10:49:21 +0200 Message-ID: References: <42F7715F.1070508@soem.dk> <42F8576D.8070200@soem.dk> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1123579404 20809 80.91.229.2 (9 Aug 2005 09:23:24 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 9 Aug 2005 09:23:24 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Aug 09 11:23:22 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1E2QJj-0002PK-12 for ged-emacs-devel@m.gmane.org; Tue, 09 Aug 2005 11:22:39 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1E2QMm-00046t-5d for ged-emacs-devel@m.gmane.org; Tue, 09 Aug 2005 05:25:48 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1E2Ps0-0007ak-0e for emacs-devel@gnu.org; Tue, 09 Aug 2005 04:54:00 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1E2PrJ-0007Vu-1z for emacs-devel@gnu.org; Tue, 09 Aug 2005 04:53:56 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1E2PrB-0007SX-2o for emacs-devel@gnu.org; Tue, 09 Aug 2005 04:53:09 -0400 Original-Received: from [64.233.182.205] (helo=nproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1E2Q1P-000163-KR for emacs-devel@gnu.org; Tue, 09 Aug 2005 05:03:43 -0400 Original-Received: by nproxy.gmail.com with SMTP id h2so14686nfe for ; Tue, 09 Aug 2005 01:49:21 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=kiyquYfeOXkByyKWvUjYDueK1VTeD/yFEkUhQlBHjCeyQEbVC0D+Z9SY7/XsTZcpDm9ETffQfOnhkIkpMda3sFo25drK+mbyHW+StCauPEOtbsXeHiNz77BSHYcSGfvlqmHqE+i2+KJtrFHYnnMlIFERbqsOLMoUrmisRMdIeiQ= Original-Received: by 10.48.250.16 with SMTP id x16mr186184nfh; Tue, 09 Aug 2005 01:49:21 -0700 (PDT) Original-Received: by 10.48.250.5 with HTTP; Tue, 9 Aug 2005 01:49:21 -0700 (PDT) Original-To: Lars Hansen In-Reply-To: <42F8576D.8070200@soem.dk> Content-Disposition: inline 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:41754 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:41754 On 8/9/05, Lars Hansen wrote: > I guess it does not have to be automatically buffer local. But I am not > shure what the advantages/disadvantages of either choice are. Well, the reason `make-local-variable' and `make-variable-buffer-local' both exists is, I think, that in some circumstances the default value of the variable is gonna weight more than local changes (i.e, the local changes are going to be few and far between), and in other cases the variable is going to have frequent buffer-local modifications. Using the latter style when the former works is not "bad", but it's a bit wasteful. In this case, I think the former case is much more frequent; the user, or the mode programmer, can always use `make-local-variable' to force their way when a really local value is needed. > My motive is to make desktop as independent of other modules as > possible. I want it to be possible to add or change module foo without > having to change desktop, even if foo requires special desktop handling. Yes, that's a worthwhile goal. > But how can > desktop find out what file to load? It knows the name of the mode (major > or minor), so if the mode function is autoloaded, it can find the file > name that way. OK, I see now. --=20 /L/e/k/t/u