I may have misunderstood something very basic about Studio's regex, so any help would be appreciated.

Let's say that I want to add something to the beginning and end of a series of segments using the Find/Replace function.

I assumed that if I used "^(.*)$" as the regex find string, then each time I clicked "Find Next", I would simply move to the next segment and the entire target segment would be highlighted.

My first question is why Studio jumps over a bunch of segments each time I click "Find Next". I really do want to replace every segment in the series, not just a seemingly random selection of them.

My second question is why Studio displays the error message "Segment start/end cannot be deleted" when I actually try to replace the contents of one of the segments that is found.

My third question is why -- after the error message has been displayed -- the Find/Replace function no longer works -- for anything. Even if I try to find a word that is in one of the target segments, absolutely nothing happens when I click the "Find Next" button. I have to close and restart Studio in order to restore the Find/Replace function.

Because of these problems, I decided to make the change in two steps. First add something to the start of the segment and then to the end.

My fourth question is why using "^(.)" to find the first character at the beginning of the segment does not skip to the next segment. If the cursor is in the middle of a target segment, then clicking "Find Next" simply highlights the next character in the same target segment, it does not jump to the first character of the next segment.

My fifth question is why using "(.)$" to find the last character at the end of a segment jumps over a bunch of segments each time I click "Find Next" (just like what was happening with "^(.*)$" ).

My sixth question is why using "(\.)$" as a test to see whether I could at least find the segments ending with a real period/full stop also fails. Just like the previous string "(.)$" , it also jumps over bunches of segments each time I click "Find Next".

(I seem to recall someone having the same problem with finding segments ending with a period/full stop a few years ago. If so, then apparently it was not considered a serious enough bug to fix back then.)

I am using Studio 2017 SR1.

If I have not made a mistake in my regex strings, perhaps someone could confirm that this happens on at least one other computer, not just mine.

Best regards,
Bruce Campbell
ASAP Language Services