From: pranav@PRANAV-W2K02.i-did-not-set--mail-host-address--so-tickle-me (Pranav K. Tiwari)
Subject: nnir indices
Date: Tue, 11 Nov 2003 15:53:33 +0530 [thread overview]
Message-ID: <u65hrb3ve.fsf@PRANAV-W2K02.i-did-not-set--mail-host-address--so-tickle-me> (raw)
With help from Christoph, I got nnir/swish-e working - and I've got to say
it's the best thing since sliced bread.
swish-e indices are large, and when they grow beyond a certain size, it
becomes extremely slow to keep them up to date - because my machine starts
paging trying to update these large indices. For that reason, I keep
multiple swish-e indices, each covering a few nnml folders.
Is there a good way of passing a list of indices to nnir, instead of a
single index file?
I know *a* way of doing it, but it's a hack. I looked at nnir.el and
noticed that nnir-swish-e-additional-switches is passed to the command line
immediately after the -f <filename> field. So, I set all the additional
indices in this list, and it works fine. But, I would prefer to pass a list
to -f, rather than relying on this contrived method.
thx,
-p
reply other threads:[~2003-11-11 10:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=u65hrb3ve.fsf@PRANAV-W2K02.i-did-not-set--mail-host-address--so-tickle-me \
--to=pranav@pranav-w2k02.i-did-not-set--mail-host-address--so-tickle-me \
/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).