unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "B. T. Raven" <ecinmn@alcisp.com>
Subject: Re: w32 emacs 21.3 problem
Date: Wed, 9 Aug 2006 19:03:47 -0500	[thread overview]
Message-ID: <73dbc$44da77b7$49f1194$17962@DIALUPUSA.NET> (raw)
In-Reply-To: 1155140985.141253.264170@i42g2000cwa.googlegroups.com


<robert.thorpe@antenova.com> wrote in message
news:1155140985.141253.264170@i42g2000cwa.googlegroups.com...
B. 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(#<buffer  *load*> nil "~/.emacs" nil t)
>   load-with-code-conversion("d:/EMACS/.emacs" "~/.emacs" t t)
>   load("~/.emacs" t t)
>   #[nil "\b^[,T\x17
> ...
>
> 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=D:\EMACS
> D:\emacs\emacs-21.3\bin\runemacs.exe --debug-init
> set HOME=
>
> And running Alt-! and then the dos set command shows that HOME=D:\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.

Thanks, Robert. On my system I have to use -q instead of -Q
for --no-init-file. I knew that that would work since even with the bad
.emacs it would load the main program normally. I started commenting out
sections but almost right away I found a letter k and the beginning of a
line before the open paren. I had looked for space-k since I thought k had
to be a token. Alles in Ordnung now. Thanks again.

Ed.

      reply	other threads:[~2006-08-10  0:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-08 23:15 w32 emacs 21.3 problem B. T. Raven
2006-08-09 16:29 ` robert.thorpe
2006-08-10  0:03   ` B. T. Raven [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='73dbc$44da77b7$49f1194$17962@DIALUPUSA.NET' \
    --to=ecinmn@alcisp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).