Description of problem:
When using the search feature, clicking on a non-text file causes
errors to be spewed to the console.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create/import a project with a string in it. (Need executable!)
2. Open Search dialog and enter the string from above
3. Double-click on the search result that is an object file.
(For example, import the "pi" project and look for the string "pi".
Double-click on "pi.o" or "pi2.o".)
Opens editor and spews a bunch of errors to console:
** (<unknown>:1926): WARNING **: Invalid UTF8 string passed to
Open editor and no errors
Probably need some sort of binary file "editor" a la hexl-mode.
This, too, seems to be "fixed". The 3.0 search facilities does not
search binary files any more. Instead it gives errors about not being
able to read a binary file ("could not read file during search"). No
more errors on the terminal. I think this is satisfactory behavior.