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: frame-local variables weirdness Date: Mon, 15 Oct 2007 13:50:36 -0400 Message-ID: References: <858x65lh4m.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 1192474625 15221 80.91.229.12 (15 Oct 2007 18:57:05 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 15 Oct 2007 18:57:05 +0000 (UTC) Cc: lekktu@gmail.com, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Oct 15 20:56:55 2007 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 1IhU5y-0006dr-TP for ged-emacs-devel@m.gmane.org; Mon, 15 Oct 2007 19:51:15 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IhU5s-00063w-2m for ged-emacs-devel@m.gmane.org; Mon, 15 Oct 2007 13:51:08 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IhU5o-00063W-K7 for emacs-devel@gnu.org; Mon, 15 Oct 2007 13:51:04 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IhU5l-00062O-4e for emacs-devel@gnu.org; Mon, 15 Oct 2007 13:51:04 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IhU5l-00062L-06 for emacs-devel@gnu.org; Mon, 15 Oct 2007 13:51:01 -0400 Original-Received: from x-132-204-240-91.xtpr.umontreal.ca ([132.204.240.91] helo=ceviche.home) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IhU5a-00009Z-Nb; Mon, 15 Oct 2007 13:50:55 -0400 Original-Received: by ceviche.home (Postfix, from userid 20848) id 56B8FB41BB; Mon, 15 Oct 2007 13:50:36 -0400 (EDT) In-Reply-To: (Richard Stallman's message of "Mon\, 15 Oct 2007 12\:04\:19 -0400") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/23.0.50 (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:80943 Archived-At: > I found the discussion. I see that someone asked for a feature to > display frame-specific data in the mode line, and I decided this > general feature (with which the job could be done) was cleaner and > simpler than a specific feature which could do only that one job. That's a reasonable request, and indeed there are situations where we can lookup a variable but we cannot call a function which could potentially run arbitrary code. Maybe that's enough to keep the feature. > Since it isn't very useful, we can take it out if we cannot fix it. > But first let's try to fix it. But the above request does not mean we need to be able to mix&match let-bindings, buffer-local, and frame-local variables. If we disallowed the buffer-local&frame-local variables, the problem would disappear. This part of the language is already complex enough as it stands. Stefan