Re: nnir better than chocolate

[Harry Putnam <reader@newsguy.com>]

Francisco Solsona <solsona@deprof.fciencias.unam.mx> writes:

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

Isn't the second dot because of the (.) int the glimpseindex output files"
(.glimpse_index)

> 
> /home/reader//glimpse_index
>             ^^
> then your "glimpse-m" is not there. This is the part in nnir.el from

It turned out to be a more mundane (and dopey) reason.  In shuffling
back and forth between the old and the new versions I had somehow
managed to rename the wrong one to 'nnir-1.16.el' and so was actually
loading 'nnir-1.11.el'
> 
> 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).

Yes, I suppose it is high time I learned to use edebug.  That would
have avoided this kind of confusion.




Thanks

-- 

Harry Putnam  reader@newsguy.com