From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: Problems with Emacs21 and Oort 0.08
Date: Tue, 17 Sep 2002 12:29:32 +0200 [thread overview]
Message-ID: <ilu8z20di43.fsf@latte.josefsson.org> (raw)
In-Reply-To: <yw.ld.1032213779.fsf@gabsi.garbers.org> (Christoph Garbers's message of "17 Sep 2002 00:02:59 +0200")
Christoph Garbers <cgarbers@gmx.de> writes:
> When doing `M-x gnus', I get this backtrace[2]:
>
> Debugger entered--Lisp error: (wrong-type-argument symbolp (2))
> byte-code("\bƒ\v\0\x182ÃMˆ‚\x10\0ÄÂÅ\"ˆ\bƒ^[\0ÆÇMˆ‚ \0ÄÆÅ\"ˆ ƒ+\0ÈÉMˆ‚0\0ÄÈÅ\"ˆ ƒ;\0ÊËMˆ‚@\0ÄÊÅ\"ˆÂ‡" [mm-emacs-mule mm-mule4-p mm-enable-multibyte #[nil "ÀÁ!‡" [set-buffer-multibyte t] 2 "Set the multibyte flag of the current buffer.\nOnly do this if the default value of `enable-multibyte-characters' is\nnon-nil. This is a no-op in XEmacs."] defalias ignore mm-disable-multibyte #[nil "ÀÁ!‡" [set-buffer-multibyte nil] 2 "Unset the multibyte flag of in the current buffer.\nThis is a no-op in XEmacs."] mm-enable-multibyte-mule4 #[nil "ÀÁ!‡" [set-buffer-multibyte t] 2 "Enable multibyte in the current buffer.\nOnly used in Emacs Mule 4."] mm-disable-multibyte-mule4 #[nil "ÀÁ!‡" [set-buffer-multibyte nil] 2 "Disable multibyte in the current buffer.\nOnly used in Emacs Mule 4."]] 3)
> require(mm-util)
This looks like byte compilation error to me. They are usually caused
by compiling elisp with one flavour of emacs and using it with
another. Is the gnus package byte compiling gnus correctly for all
your installed emacsen?
next prev parent reply other threads:[~2002-09-17 10:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-16 22:02 Christoph Garbers
2002-09-17 8:25 ` Frank Schmitt
2002-09-17 10:08 ` Christoph Garbers
2002-09-17 10:29 ` Simon Josefsson [this message]
2002-09-17 10:40 ` Christoph Garbers
2002-09-17 19:41 ` Simon Josefsson
2002-09-17 22:55 ` Christoph Garbers
2002-09-18 8:37 ` Christoph Garbers
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=ilu8z20di43.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--cc=ding@gnus.org \
/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).