FindAll with single zero-length match at start-of-file breaks subsequent same search

it’s also a very obscure set of circumstances that trigger it.

I noticed it when I was trying to get a hit on every file in a directory tree matching a specific Filter using Find in Files, so that I could use the Copy Pathnames feature of Search results right-click menu.

It was the most “obvious” search I thought of doing, although later (after the strange behavior noticed) I changed to \z and that worked (on a repetitive basis) to achieve my goal.

Neither \A (first time) nor \z works on zero-length files, though. I suppose I can accept that a search that is supposed to find something, doesn’t find that certain something, because it is searching a void.

I suppose I should create an official issue about this.

Further testing suggests that the odd behavior is triggered by a search that results in a single, zero-length match at the very beginning of a file. (It doesn’t have to be \A; for example, a look-ahead that only matches in that position will do.)

Following that, the next Find All will ignore a zero-length match at the beginning of the file (though other matches, if any, including zero-length matches not at the beginning of the file, will still be reported).

I haven’t found the time and concentration yet to see if there is an identifiable reason in the code. It’s definitely unexpected behavior, but it’s also a very obscure set of circumstances that trigger it.