From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Specifiers Date: Thu, 29 May 2008 22:21:46 -0400 Message-ID: References: <5CB5F5E5-9239-40A8-A3B2-5F49B94E27B7@gmail.com> <85lk1ui3i0.fsf@lola.goethe.zz> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1212114134 29591 80.91.229.12 (30 May 2008 02:22:14 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 30 May 2008 02:22:14 +0000 (UTC) Cc: david.reitter@gmail.com, emacs-devel@gnu.org, miles@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri May 30 04:22:55 2008 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 1K1uGa-0001WG-EX for ged-emacs-devel@m.gmane.org; Fri, 30 May 2008 04:22:52 +0200 Original-Received: from localhost ([127.0.0.1]:40739 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K1uFo-0005nc-JO for ged-emacs-devel@m.gmane.org; Thu, 29 May 2008 22:22:04 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K1uFk-0005nP-Ic for emacs-devel@gnu.org; Thu, 29 May 2008 22:22:00 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K1uFj-0005nD-6l for emacs-devel@gnu.org; Thu, 29 May 2008 22:21:59 -0400 Original-Received: from [199.232.76.173] (port=57405 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K1uFj-0005nA-1i for emacs-devel@gnu.org; Thu, 29 May 2008 22:21:59 -0400 Original-Received: from 206-248-174-248.dsl.teksavvy.com ([206.248.174.248]:40051 helo=ceviche.home) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1K1uFc-0006Zy-AO; Thu, 29 May 2008 22:21:52 -0400 Original-Received: by ceviche.home (Postfix, from userid 20848) id 12857B41E2; Thu, 29 May 2008 22:21:46 -0400 (EDT) In-Reply-To: (Richard M. Stallman's message of "Thu, 29 May 2008 22:08:42 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 3) 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:98033 Archived-At: > - what should (setq var val) do? > currently is magically uses either the global or the current-buffer > locus depending on whether the variable is already buffer-local. > but if it's buffer-local and frame-local, which setting should > be changed? > - how does it interact with make-variable-buffer-local? > I.e. if a variable is just window-local and you do (setq var val), is > it going to be made buffer-local? > - what about `let'? This one is really fun! > All these issues arise already with the current features, Yes, pretty much, except we don't have to worry about combinations of buffer-local with other forms of foo-local at the same time (well, supposedly we have to worry about it for buffer-local + frame-local, but we already know we don't handle that correctly). > and won't get any worse with the proposed new feature. Try it. > ISTR that there is already code in specbind to try to DTRT > for some of these. Yes, there's already a fair bit of code trying to get things to work right for buffer-local variables (in specbind and a bunch of other places). It's already pretty complex just like that. Stefan