I have just noticed an odd behavior with Find and Replace: if any matches are found, the replaced string is first inserted at the current insertion point (unexpected), and only afterwards used to replace any of the found matches. Illustrated below:
Step 3: Hit [Replace] button a second time. Feature resumes expected behavior, replacing the first occurrence of search string.
Can anyone explain the reasoning behind this behavior? This feels like a bug. Is this a bug? (Running Mojave).