From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Newsgroups: gmane.emacs.devel Subject: byte-compiling an elisp-file fails in Emacs 22.1 (reproducable) Date: Fri, 6 Jul 2007 19:05:52 +0200 Message-ID: References: <86bqf9om2y.fsf@lola.quinscape.zz> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1183741572 23306 80.91.229.12 (6 Jul 2007 17:06:12 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 6 Jul 2007 17:06:12 +0000 (UTC) To: Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jul 06 19:06:11 2007 connect(): Connection refused 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 1I6rFs-0002ZM-CE for ged-emacs-devel@m.gmane.org; Fri, 06 Jul 2007 19:06:04 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I6rFr-0007Se-Un for ged-emacs-devel@m.gmane.org; Fri, 06 Jul 2007 13:06:03 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1I6rFn-0007MX-6L for emacs-devel@gnu.org; Fri, 06 Jul 2007 13:05:59 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1I6rFl-0007KH-Fx for emacs-devel@gnu.org; Fri, 06 Jul 2007 13:05:58 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I6rFl-0007K0-8W for emacs-devel@gnu.org; Fri, 06 Jul 2007 13:05:57 -0400 Original-Received: from world1.sdm.de ([192.76.162.229]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1I6rFk-00067g-N3 for emacs-devel@gnu.org; Fri, 06 Jul 2007 13:05:56 -0400 Original-Received: from [10.40.232.18] (helo=mucns1.muc.sdm.de) by world1.sdm.de with esmtp (MTA) id 1I6rFi-0001uN-19 for emacs-devel@gnu.org; Fri, 06 Jul 2007 19:05:54 +0200 Original-Received: from localhost ([127.0.0.1] helo=sdmmail1.sdm.de) by mucns1.muc.sdm.de with esmtp (MTA) id 1I6rFh-0002lL-VU for emacs-devel@gnu.org; Fri, 06 Jul 2007 19:05:54 +0200 Original-Received: from mucmail1.sdm.de ([193.102.180.175]) by sdmmail1.sdm.de with Microsoft SMTPSVC(6.0.3790.1830); Fri, 6 Jul 2007 19:05:53 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message In-Reply-To: <86bqf9om2y.fsf@lola.quinscape.zz> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: byte-compiling an elisp-file fails in Emacs 22.1 (reproducable) Thread-Index: AcezzdC0HNXSExLnQIyie0YbvACL8AMILOsQ X-OriginalArrivalTime: 06 Jul 2007 17:05:53.0211 (UTC) FILETIME=[E91820B0:01C7BFEF] X-detected-kernel: Linux 2.4-2.6 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:74413 Archived-At: Hi all, 1. using Emacs 22.1 for MS Windows. 2. starting Emacs with runemacs --quick so no private setup-stuff is loaded - just a plain and fresh Emacs 3. Opening my .emacs with C-x C-f 4. calling "Byte-compile This File" from the menu "Emacs-lisp" Get the error "Symbol's function definition is void: = compilation-forget-errors" When activating "Enter debugger on error" vefore step 4, i get the = following backtrace: Debugger entered--Lisp error: (void-function compilation-forget-errors) compilation-forget-errors() byte-compile-log-file() byte-compile-from-buffer(# "c:/home/.emacs") byte-compile-file("c:/home/.emacs") emacs-lisp-byte-compile() call-interactively(emacs-lisp-byte-compile) Even explicitly loading compile.el (which defines this function) before = byte-compiling doesn't fix it.... Is this a known bug?=20 Anyway it's an anoying bug which makes the new Emacs 22 quite unuseable = for me because i do a lot of elisp-programming and byte-compiling.... Is there a known work-around for that problem? Thanks in advance! Klaus