Re: nnir oddity in group names

[Harry Putnam <reader@newsguy.com>]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> 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?

Yup, thats the one.
> 
> 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.

I think  not.  Heres why... further experiments show:

1) C-u G G <gnus;unplugged><RET> <gnu.emacs.gnus> <RET> fails
2) C-u G G <gnus;unplugged><RET> <gnus> <RET> works

So far those two experiments would tend to confirm you hypothesis.. 
read on.

3) C-u G G <gnus;unplugged><RET> <gnu/emacs/gnus> <RET> works
(Same length query string works in number three)

> 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.

Didn't follow the last two suggestions... sorry.