[recoll-user] Re: Something special / unusual about .cpp suffix?

  • From: Randy Kramer <rhkramer@xxxxxxxxx>
  • To: recoll-user@xxxxxxxxxxxxx
  • Date: Tue, 20 Sep 2011 16:15:38 -0400

jf,

Thanks!  I was doing something dumb--I guess the problem was that I had first 
tried to index without an entry for .cpp in the mimemap file, and then never 
used the -z option to get rid of the old index / database.

I used the -z, and all is well.

Thanks again!

Randy Kramer

On Tuesday 20 September 2011 11:15:23 am jfd@xxxxxxxxxx wrote:
> Randy Kramer writes:
>  > Although I could be doing something dumb, I've tried this quite a few
>  > times. Searches for all kinds of things (e.g., #include statements) work
>  > fine for scintilla/SciTE, but don't work for recoll.
>  >
>  > Any hints appreciated!

> Mmmouark ark! ark! ark! (sardonic laugh) Recoll text is unsearchable,
> that's part of the plan for word domination.
>
> More seriously, set up the recoll.conf that you use for indexing the recoll
> source so that you get a detailed log:
>   logfilename = /tmp/mylogforrecoll
>   loglevel = 6
>
> Then perform a full indexing pass:
> recollindex -z -c /path/to/the/confdir/for/indexing/recoll
>
> And look in the file to see what happens to .cpp files (to make things
> easier, search for a file whose name won't be listed as a message origin,
> like for example ssearch_w.cpp).
>
> If nothing obvious appears, please send me the log fragment for one of
> these files. Maybe I'll see something, else we'll check how you perform the
> queries too.
>
> By the way, with recent versions (at least since 1.14), you should not have
> to change mimemap all that much, .c, .cpp, .cc, and .h files are supposedly
> indexed as text (I just added .cxx).




Other related posts: