From: Josh Huber <huber@alum.wpi.edu>
Subject: Re: nnir and swish++?
Date: 22 Jun 2001 09:59:53 -0400 [thread overview]
Message-ID: <87d77wboo6.fsf@mclinux.com> (raw)
In-Reply-To: <vafg0cs96lx.fsf@lucy.cs.uni-dortmund.de>
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> Can you delete nnir.elc, start a new Emacs, and produce a more
> complete backtrace?
>
> And also, which version of nnir.el is it? If not 1.68, does that one
> work better?
Thanks, upgrading fixed the problem...nnir is _finally_ working.
After going through 2 previous databases (freeWAIS-sf and glimpse),
I've finally found one that doesn't segfault randomly on my powerpc
laptop. :)
Thanks for the help...
--
Josh Huber
next prev parent reply other threads:[~2001-06-22 13:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-20 21:31 Josh Huber
2001-06-21 7:47 ` Marco Lonsing
2001-06-21 14:06 ` Karl Kleinpaste
2001-06-21 14:44 ` Josh Huber
2001-06-21 15:15 ` Karl Kleinpaste
2001-06-21 18:46 ` Wes Hardaker
2001-06-22 10:00 ` Kai Großjohann
2001-06-22 13:59 ` Josh Huber [this message]
2002-10-21 3:50 ` Christoph Conrad
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=87d77wboo6.fsf@mclinux.com \
--to=huber@alum.wpi.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).