GNOME Bugzilla – Bug 672900
Search should not start over while typing
Last modified: 2014-07-06 03:41:36 UTC
I am using evince to read big PDF books of several 100 pages. When searching the search is restarted on every letter in the search box. However, as long as I am not deleting characters evince does not have to start over. Imagine search for "term". If it starts searching for "te", evince should just filter the first hits when I enter the next characters.
still valid.
It can be a problem in the backend, maybe related the fonts in the document. Do you have a test case? I tried with PDF Reference 1.7, which has 1310 pages and it is pretty fast. http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/pdf/pdfs/pdf_reference_1-7.pdf
*** This bug has been marked as a duplicate of bug 667569 ***
Germán thanks for looking into this. Howver, the bugs are not duplicates. Open for example the document at <http://dspace.mit.edu/bitstream/handle/1721.1/48833/planningsystemsc00rama.pdf>. Search for "Plann". Results are found. However, when entering an "i" in addition to search for "Planni" the document is search again, although it would have been enough to just compare the hits of the previous search again.
(In reply to comment #4) > Germán thanks for looking into this. > > Howver, the bugs are not duplicates. > > > Open for example the document at > <http://dspace.mit.edu/bitstream/handle/1721.1/48833/planningsystemsc00rama.pdf>. > > Search for "Plann". Results are found. However, when entering an "i" in > addition to search for "Planni" the document is search again, although it would > have been enough to just compare the hits of the previous search again. Agreed. Instead, this bug report is a duplicate of bug 607907. That title is not as informative as this title though. I will edit the title of that bug.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 607907 ***