From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: describe-variable gets the defining library wrong Date: Fri, 19 Jun 2009 10:27:11 -0700 Message-ID: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1245432455 22688 80.91.229.12 (19 Jun 2009 17:27:35 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 19 Jun 2009 17:27:35 +0000 (UTC) To: Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jun 19 19:27:32 2009 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 1MHhsC-0002Al-6I for ged-emacs-devel@m.gmane.org; Fri, 19 Jun 2009 19:27:32 +0200 Original-Received: from localhost ([127.0.0.1]:56928 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MHhsB-0005Mt-D1 for ged-emacs-devel@m.gmane.org; Fri, 19 Jun 2009 13:27:31 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MHhs2-0005JG-Vd for emacs-devel@gnu.org; Fri, 19 Jun 2009 13:27:23 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MHhry-0005Cw-FR for emacs-devel@gnu.org; Fri, 19 Jun 2009 13:27:22 -0400 Original-Received: from [199.232.76.173] (port=44721 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MHhry-0005Ca-7K for emacs-devel@gnu.org; Fri, 19 Jun 2009 13:27:18 -0400 Original-Received: from acsinet11.oracle.com ([141.146.126.233]:32198) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MHhrx-0001lx-NJ for emacs-devel@gnu.org; Fri, 19 Jun 2009 13:27:18 -0400 Original-Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by acsinet11.oracle.com (Switch-3.3.1/Switch-3.3.1) with ESMTP id n5JHSF3g009056 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 19 Jun 2009 17:28:16 GMT Original-Received: from abhmt001.oracle.com (abhmt001.oracle.com [141.146.116.10]) by acsinet15.oracle.com (Switch-3.3.1/Switch-3.3.1) with ESMTP id n5JHSYC3000359 for ; Fri, 19 Jun 2009 17:28:34 GMT Original-Received: from dradamslap1 (/24.5.177.54) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 19 Jun 2009 10:27:11 -0700 X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcnxAy3ycFmeK6UjSYiw+Tf+VN50FA== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 X-Source-IP: abhmt001.oracle.com [141.146.116.10] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A010201.4A3BCA70.015E:SCFSTAT5015188,ss=1,fgs=0 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 1) 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:111593 Archived-At: I haven't found a recipe to reproduce this, but it happens to me quite often with Emacs 23: `describe-variable' says "foo is a variable defined in `bar.el'" when foo is not defined in `bar.el' at all, or at least not most recently. I've even seen it happen when `bar.el' has only a byte-compiler quieter sexp, such as this, which should hardly count as a definition: (defvar foo). This is a mystery, to me. I've also seen "defined in `.emacs'", when that is not at all where the variable is defined. I suppose this is a fallback (copout), if Emacs can't tell where the variable was really defined. That's understandable, I guess. (But not very useful, and still misleading - maybe it's better to say nothing if we know nothing.) But saying that the current definition is in library bar.el when it was last defined in toto.el is wrong. Emacs has always had some degree of difficulty reporting this, but it seems like this has gotten worse in Emacs 23. Does anyone else see this behavior, or is it just me? Sorry I don't have a recipe to reproduce this yet.