From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.bugs Subject: bug#7087: 24.0.50; cannot customize default-frame-alist - it says value is nil but it is not Date: Thu, 23 Sep 2010 13:35:25 -0700 Message-ID: <4433C2799F32480A90E36306C8157831@us.oracle.com> References: <5567061AAE0C434CA177126DEC0D1B02@us.oracle.com> <4C9B42E2.4040404@gmx.at> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1285274510 26805 80.91.229.12 (23 Sep 2010 20:41:50 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 23 Sep 2010 20:41:50 +0000 (UTC) Cc: 7087@debbugs.gnu.org To: "'martin rudalics'" Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Sep 23 22:41:46 2010 Return-path: 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 ) id 1Oysbq-0003GK-RM for geb-bug-gnu-emacs@m.gmane.org; Thu, 23 Sep 2010 22:41:39 +0200 Original-Received: from localhost ([127.0.0.1]:45839 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Oysbq-0002LD-AE for geb-bug-gnu-emacs@m.gmane.org; Thu, 23 Sep 2010 16:41:38 -0400 Original-Received: from [140.186.70.92] (port=45593 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OysbK-000225-Ru for bug-gnu-emacs@gnu.org; Thu, 23 Sep 2010 16:41:08 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OysbH-0002Qm-G3 for bug-gnu-emacs@gnu.org; Thu, 23 Sep 2010 16:41:06 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:44666) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OysbH-0002Qi-DL for bug-gnu-emacs@gnu.org; Thu, 23 Sep 2010 16:41:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.69) (envelope-from ) id 1OysUU-0006Xo-A5; Thu, 23 Sep 2010 16:34:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: "Drew Adams" Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-To: owner@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 23 Sep 2010 20:34:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 7087 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 7087-submit@debbugs.gnu.org id=B7087.128527401925148 (code B ref 7087); Thu, 23 Sep 2010 20:34:02 +0000 Original-Received: (at 7087) by debbugs.gnu.org; 23 Sep 2010 20:33:39 +0000 Original-Received: from localhost ([127.0.0.1] helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OysU7-0006XZ-G9 for submit@debbugs.gnu.org; Thu, 23 Sep 2010 16:33:39 -0400 Original-Received: from rcsinet10.oracle.com ([148.87.113.121]) by debbugs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OysU5-0006XT-Td for 7087@debbugs.gnu.org; Thu, 23 Sep 2010 16:33:38 -0400 Original-Received: from rcsinet13.oracle.com (rcsinet13.oracle.com [148.87.113.125]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id o8NKaErD026187 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 23 Sep 2010 20:36:15 GMT Original-Received: from acsmt354.oracle.com (acsmt354.oracle.com [141.146.40.154]) by rcsinet13.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o8NII1HQ009882; Thu, 23 Sep 2010 20:36:13 GMT Original-Received: from abhmt003.oracle.com by acsmt355.oracle.com with ESMTP id 632029391285274126; Thu, 23 Sep 2010 13:35:26 -0700 Original-Received: from dradamslap1 (/130.35.178.194) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 23 Sep 2010 13:35:26 -0700 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <4C9B42E2.4040404@gmx.at> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994 Thread-Index: ActbUOPyMohPf1q9SUGNrezA/+4fKgAC8evQ X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.11 Precedence: list Resent-Date: Thu, 23 Sep 2010 16:34:02 -0400 X-detected-operating-system: by eggs.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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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:40384 Archived-At: > > In this Emacs 24 build, M-x customize-option > > default-frame-alist gives a Customize buffer that shows the > > value of the option as nil and says > > "this option has been changed outside the customize > > buffer. (mismatch)". However, C-h v default-frame-alist shows > > it has a non-nil value: > > > > ((foreground-color . "Black") > ... > > (icon-type) > > nil > ^^^ Good catch. I didn't notice that. Dunno how that happened. However, if the value does become something like that for some reason, then the displayed value should be the complete sexp that is the value, not just one little part of it. So there is apparently a bug present in any case - probably in the customize code. > `default-frame-alist' has the customization type > > (repeat (cons :format "%v" > (symbol :tag "Parameter") > (sexp :tag "Value")))) > > so obviously this "nil" here will cause a mismatch. Yes, indeed. Again, dunno how the nil value got there. Probably something that happened during the session. Perhaps there is a bug elsewhere that introduced that. Note though that the nil entry did not seem to in any way interfere with the use/behavior of `default-frame-alist'. And that makes sense. FWIW, I've checked all of my own code to be sure that the nil alist entry could not have come from it. In all cases it uses a cons. I did not check all other 3rd-party code I might load, but if I had to guess I'd guess that this came somehow from the vanilla Emacs 24 code, mainly because I've never come across this before. Anyway, to follow up more - I cannot reproduce the problem. In subsequent sessions I do not see it. So we can either close this or keep it as info in case we later learn of other cases where a nil entry gets introduced. For the moment I have no idea how that happened, unfortunately, and I never saw it previously. I should have tried in a new session before posting the bug, and I should have noticed the nil entry. But at least now we know to keep our eyes out for something that might introduce a nil entry. Thx.