GNOME Bugzilla – Bug 694056
Regression: option --find in the command line does not work anymore
Last modified: 2013-02-19 07:09:20 UTC
This seems an old regression because I can reproduce with 3.4.0 and master (3.7.5). 1. Open a PDF (with text searchable text). $ evince document.pdf & 2. Open the same document with some text to find: $ evince --find=text document.txt Current result: The document is refreshed, but nothing seems to be happening. Expected result: Highlight the text if found, with the search pane opened.
It is not necessary to call it twice to reproduce the bug: $ evince --find=text document.txt Just open the document as if the option did not exist.
The --find switch does work, but only after engaging the search. See here for reference: https://www.youtube.com/watch?v=GeeIBP8PbGE Recoll (the full-text search tool used in the video above) passes the search string to evince via the --find=STRING switch. The advantage of this behaviour in the use case above is that it allows the user to check the page for any obvious hits before engaging a CPU intensive search. So while it makes sense to fix this regression it might also be a good idea to implement a switch between directly engaging a search and only passing the search term to the search field (e.g. --find=STRING and --searchfield=STRING). Possible duplicate: https://bugzilla.gnome.org/show_bug.cgi?id=604327 These are related bug reports: https://bugzilla.gnome.org/show_bug.cgi?id=611619 https://bugzilla.gnome.org/show_bug.cgi?id=694143
*** This bug has been marked as a duplicate of bug 604327 ***