Re: nnir oddity in group names

[Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)]

On 04 Aug 2000, Harry Putnam wrote:

> Nnir fails if I enter the group name as in the first (t.awk)
>    example: comp.unix.questions
> 
> And will only work if I use the actual unix style name:
>    comp/unix/questions

Hm.  Amazing.  You are talking about entering the group spec, right?
This parameter that you are asked for when you do C-u G G but not with
just G G?

nnir-run-glimpse calls glimpse like this:

    glimpse -H $h -W -l -y ... -F "$p;$g" $query

$h means nnir-glimpse-home, $p means nnir-glimpse-remove-prefix, and
$g is the group spec that you enter after C-u G G.

It appears to me that entering `foo.bar' for the group spec will match
directory names `foo/bar' as well as `fooXbar', say.

But there is one difference between `t.awk' and `comp.unix.questions':
the length.  I think there is a rather short length limit on Glimpse
queries.  Maybe 16 characters?  Or 32?

Do you think that this might be the problem?  I wish there was a way
around this, but I don't know of one.

Hm.

But maybe I could use grep:

    glimpse -H $h -W -l -y -F $p $query | grep -e $g

Do you think that this might help?  Could somebody try this to see if
it does?

Another idea might be to use the keep-lines Lisp function to do the
job of grep.  This might be even better, since call-process might not
be able to do the pipe thing.

kai
-- 
I like BOTH kinds of music.