From: Francisco Solsona <solsona@deprof.fciencias.unam.mx>
Cc: ding@gnus.org
Subject: Re: nnir better than chocolate
Date: 12 Aug 1998 09:48:04 -0500 [thread overview]
Message-ID: <m2iujydzob.fsf@deprof.fciencias.unam.mx> (raw)
In-Reply-To: Harry Putnam's message of "11 Aug 1998 20:41:00 -0700"
Harry Putnam <reader@newsguy.com> writes:
> Kai Grossjohann <grossjohann@amaunet.cs.uni-dortmund.de> writes:
[...]
> Args out of range: ["can't open glimpse index-file .home.reader..glimpse_index
> (use -H to give an index-directory or run 'glimpseindex' to make an index)
> " 1000], 2
> Is the ".home.reader..glimpse_index" notation, an indication of a problem?
Yes. Those "." are actually "/" (they get substituted by
nnir), so the path actually is:
/home/reader//glimpse_index
^^
then your "glimpse-m" is not there. This is the part in nnir.el from
where glimpse gets called:
(call-process nnir-glimpse-program
nil ; input from /dev/null
t ; output
nil ; don't redisplay
"-H" nnir-glimpse-home ; search home dir
^^^^^^^^^^^^^^^^^^
...
note that the value of nnir-glimpse-home is inserted "as is". Your
problem then can only reside on the setting of that variable. I have,
(require 'nnir)
(setq nnir-glimpse-home "/path/to/index")
...
and it works fine. Why don't you load nnir.el (not nnir.elc) and then
edebug nnir-run-glimpse, that way you'll be sure of what value of
nnir-glimpse-home is using (and why).
hth,
Francisco
--
When people post source code in gnu.emacs.sources,
please do not curse at them. Please just keep silent.
--Richard Stallman
next prev parent reply other threads:[~1998-08-12 14:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-07 21:24 Harry Putnam
1998-08-11 15:18 ` Kai Grossjohann
1998-08-11 15:19 ` Kai Grossjohann
1998-08-11 15:26 ` Norbert Koch
1998-08-12 3:41 ` Harry Putnam
1998-08-12 14:48 ` Francisco Solsona [this message]
1998-08-12 21:35 ` Harry Putnam
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=m2iujydzob.fsf@deprof.fciencias.unam.mx \
--to=solsona@deprof.fciencias.unam.mx \
--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).