#221 Unnecessary Grep Error Messages

[kgmccoy]

When scanning all folders in a drive, (C:) Grep pops up numerous error messages complaining about folders that do not exist. I don't know if it chokes on linked folders or long path names, but it is pretty annoying.

It is not important that Grep could not find a given folder, since all we care about is the contents of target file types. Could a Grep setting be added to ignore unreachable folders - or just stop logging them?

See the attached screenshot where I Grep-scan my C: drive for the word "Standalone" and Grep presents me with a long list of "does not exist" errors.

[Thomas Mueller]

You can count yourself lucky that it no longer shows a separate message for every error as it was in the original Grep when I took it over. But yes, you are right: That is still not optimal.

(On the other hand: This is not a bug but a feature request. It currently works as designed.)

[kgmccoy]

Should I move/recreate this report as a feature request?

[Thomas Mueller]

No, it's fine. I can always move the ticket (which I found out only recently). It's just difficult to recreate the problem.

[kgmccoy]

To recreate the issue, do a grep Directory search for an impossible string - something like "XYZZY" with C:\ as the path and Search Subdirectories turned on with no depth limit. The actual search string is not important, but an impossible one will cut down on the "noise".

Yes, the search will take a while :-(

It might be easier to put a checkbox on the search form that suppresses missing-path warnings. Make the setting sticky.

A side-quest for you might be skipping the Grep Search cache folders when searching that drive ;-)

[Thomas Mueller]

I just tried to reproduce the problem in this way. No luck, it just found nothing, no error message.

It might be easier to put a checkbox on the search form that suppresses missing-path warnings.

I could do that, but I would have no way to test it.

[Thomas Mueller]

Ticket moved from /p/gexperts/bugs/461/

[Thomas Mueller]

implemented in revision #5315 by switching to the GExperts TGXMsgBoxAdaptor framework. The error dialog now has a checkbox to disable that message.

(Note: This did not make it into the GExperts release from today.)