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 11:59:35 +0200 Message-ID: References: <42F7715F.1070508@soem.dk> <42F8576D.8070200@soem.dk> <857jevwj6d.fsf@lola.goethe.zz> 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 1123582520 28819 80.91.229.2 (9 Aug 2005 10:15:20 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 9 Aug 2005 10:15:20 +0000 (UTC) Cc: Lars Hansen , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Aug 09 12:15:17 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1E2R7b-0007xm-D6 for ged-emacs-devel@m.gmane.org; Tue, 09 Aug 2005 12:14:11 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1E2RAe-00051S-7R for ged-emacs-devel@m.gmane.org; Tue, 09 Aug 2005 06:17:20 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1E2Qxw-0001Th-LG for emacs-devel@gnu.org; Tue, 09 Aug 2005 06:04:12 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1E2Qxs-0001RZ-Rl for emacs-devel@gnu.org; Tue, 09 Aug 2005 06:04:10 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1E2Qxs-0001QQ-C2 for emacs-devel@gnu.org; Tue, 09 Aug 2005 06:04:08 -0400 Original-Received: from [64.233.182.201] (helo=nproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1E2R7N-0006L6-QB for emacs-devel@gnu.org; Tue, 09 Aug 2005 06:13:58 -0400 Original-Received: by nproxy.gmail.com with SMTP id h2so19573nfe for ; Tue, 09 Aug 2005 02:59:35 -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=rBstm4085NNxo1/7W2PaQgrELCYmBst5FrlYqI/c0G9aubfzgzIPYvPo5uGGtfziTR2rslM27ZQFYVSbV2gLZZ7a6++dBhp5LKsx80qojotDFz3Zz3fxER2nv93HnePtl6QRA5xMfAPXtmcAwHLcvGhlGMm5wRwm4ZzYKy08Nkg= Original-Received: by 10.48.43.14 with SMTP id q14mr64398nfq; Tue, 09 Aug 2005 02:59:35 -0700 (PDT) Original-Received: by 10.48.250.5 with HTTP; Tue, 9 Aug 2005 02:59:35 -0700 (PDT) Original-To: David Kastrup In-Reply-To: <857jevwj6d.fsf@lola.goethe.zz> 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:41763 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:41763 On 8/9/05, David Kastrup wrote: > I tend to use make-variable-buffer-local when a variable is tracking > some state of a buffer, such that it would always be an error if two > buffers shared such a variable. Sure. For example, any variable that tracks something related to external characteristics of the buffer (or the buffer's associated file, if any) must usually be automatically buffer-local. In the case at hand, I think most buffers will want the same `desktop-locals-to-save'. I can imagine buffer X in mode M wanting to save its value of LOCAL-VAR-1, and buffer Y also in mode M wanting to save its own LOCAL-VAR-1, but it will be less frequent for buffer X to want to save LOCAL-VAR-1 and for buffer Y *not* wanting to save it. --=20 /L/e/k/t/u