Gnus development mailing list
 help / color / mirror / Atom feed
From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Nearly impossible to start up recent Oort.
Date: Fri, 08 Feb 2002 00:03:13 -0500	[thread overview]
Message-ID: <2npu3gimzy.fsf@zsh.cs.rochester.edu> (raw)
In-Reply-To: <m2k7tolhcg.fsf@asfast.com> (Lloyd Zusman's message of "Thu, 07 Feb 2002 23:37:03 -0500")

Lloyd Zusman <ljz@asfast.com> writes:

> I can barely start up the latest CVS versions of Oort.  I have to try
> over and over, and maybe one out of 10 times or so, gnus finally comes
> up.  When it doesn't start, either the XEmacs window completely
> disappears, or els I get the following error.  I'm using XEmacs 21.4.3
> under RedHat Linux 7.2.
>
> Any ideas?
>
> Thanks in advance.
>
> Signaling: (invalid-function 67399686)
>   67399686("" #<compiled-function (file orig-file) "...(17)" [orig-file file nnmail-split-incoming nnml-save-mail nil nnmail-get-split-group (directory :path "/home/ljz/Groups/" :suffix ".in") nnml-active-number] 7> t)
>   gnus-byte-compile((lambda (file orig-file) (nnmail-split-incoming file (quote nnml-save-mail) (quote nil) (if ... nil ...) (quote nnml-active-number))))

You can get around the problem with (setq gnus-use-byte-compile nil).
If it works, probably there is a bug in the XEmacs byte-compile code.

ShengHuo



  reply	other threads:[~2002-02-08  5:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-08  4:37 Lloyd Zusman
2002-02-08  5:03 ` ShengHuo ZHU [this message]
2002-02-08 13:10   ` Lloyd Zusman
2002-02-08 19:12     ` ShengHuo ZHU
2002-02-08 20:03       ` Karl Kleinpaste
2002-02-09  1:41         ` Russ Allbery
2002-02-09  2:58           ` Len Blanks
2002-02-09 10:27       ` Vincent Bernat
2002-02-09  1:40   ` Russ Allbery
2002-02-09  5:16     ` Lloyd Zusman

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=2npu3gimzy.fsf@zsh.cs.rochester.edu \
    --to=zsh@cs.rochester.edu \
    /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).