From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: robert.thorpe@antenova.com Newsgroups: gmane.emacs.help Subject: Re: w32 emacs 21.3 problem Date: 9 Aug 2006 09:29:45 -0700 Organization: http://groups.google.com Message-ID: <1155140985.141253.264170@i42g2000cwa.googlegroups.com> References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1155141634 26167 80.91.229.2 (9 Aug 2006 16:40:34 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 9 Aug 2006 16:40:34 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Aug 09 18:40:32 2006 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1GAr6V-0000Gm-U6 for geh-help-gnu-emacs@m.gmane.org; Wed, 09 Aug 2006 18:40:24 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GAr6V-0003BR-6q for geh-help-gnu-emacs@m.gmane.org; Wed, 09 Aug 2006 12:40:23 -0400 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!postnews.google.com!i42g2000cwa.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 49 Original-NNTP-Posting-Host: 213.94.228.210 Original-X-Trace: posting.google.com 1155140990 11681 127.0.0.1 (9 Aug 2006 16:29:50 GMT) Original-X-Complaints-To: groups-abuse@google.com Original-NNTP-Posting-Date: Wed, 9 Aug 2006 16:29:50 +0000 (UTC) In-Reply-To: User-Agent: G2/0.2 X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6,gzip(gfe),gzip(gfe) X-HTTP-Via: 1.0 EMF3ASPROXY03 Complaints-To: groups-abuse@google.com Injection-Info: i42g2000cwa.googlegroups.com; posting-host=213.94.228.210; posting-account=hWoAPxMAAAAnBKSBz1ZivwUPPjEuve7bvVCHZQ8rhrluPfwcBJd92w Original-Xref: shelby.stanford.edu gnu.emacs.help:140955 Original-To: help-gnu-emacs@gnu.org X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:36580 Archived-At: B=2E T. Raven wrote: > After getting a "Invalid VxD dynamic link error ..." on a win98 > installation, I reinstalled windows (conservatively) and tried a few other > things to no avail. Pulling and replacing a memory stick fixed the win98 > problem but now I see a debug backtrace instead of getting the .emacs > functionality: > > Debugger entered--Lisp error: (void-variable k) > ;; my comment: variable k is some artifact. There is none such in the > .emacs > eval-buffer(# nil "~/.emacs" nil t) > load-with-code-conversion("d:/EMACS/.emacs" "~/.emacs" t t) > load("~/.emacs" t t) > #[nil ",T > ... > > The .emacs starts with: > > ;; -*- coding: utf-8 -*- > > and has many exotic characters in it and I suspect that I may have wiped > out some of the .nls codepage files that are needed for unicode support. > The registry, though, looks like they are still installed. > > Emacs is invoked in a batch file if that makes a difference: > > set HOME=3DD:\EMACS > D:\emacs\emacs-21.3\bin\runemacs.exe --debug-init > set HOME=3D > > And running Alt-! and then the dos set command shows that HOME=3DD:\EMACS= is > being set correctly in this shell so I'm reading the .emacs that I think I > am. > > Before my memory problems this .emacs has been working flawlessly (mostly) > for many months. > > Does any of you have any ideas on where I can start looking for a > solution? Start by seeing if emacs -Q works, if so then it's something in your .emacs file at least triggering the bug. Then you can proceed by chopping your .emacs file in half. Comment the bottom half out, see if it works, then try with the top half commented out. Then split the offending half into halves and continue until you find the line triggering the behaviour.