From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Please don't bind "obarray" (gnus-agent)
Date: Wed, 03 Mar 2004 19:39:57 +0100 [thread overview]
Message-ID: <rj8yihrczm.fsf@sheridan.dina.kvl.dk> (raw)
I hard a hard time tracking down a but that prevented me from running
Gnus after the latest cvs update.
Apparently gnus-agent-read-local and gnus-agent-save-local bind
obarray. When one of them for some reason needed to ask for a "coding
system for file", emacs could not find the symbols it needed. They
are apparently in the obarray. And gave an error. Which could not be
caught by the debugger, because debugging uses obarray too.
The *Messages* buffer worked, so I eventually found the problem by
inserting lots of "message" calls.
I change the two functions to use "my-obarray" instead. I'm not
actually sure how the functions work, so I hope I did not damage
anything.
next reply other threads:[~2004-03-03 18:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 18:39 Per Abrahamsen [this message]
2004-03-04 1:03 ` Kevin Greiner
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=rj8yihrczm.fsf@sheridan.dina.kvl.dk \
--to=abraham@dina.kvl.dk \
/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 NNTP newsgroup(s).