Quote:
Originally Posted by KevinH
Still not sure what the "save as" is contributing to this.
|
Honestly, I've been doing this for so long that it actually took me a moment to remember/reconstruct
why I do this in that order...
Basically, where there are only a few (less than 10) matches for a given search or where it's a simple bulk replace, I'll cycle through the document, not caring where in the document the search starts. These searches (with limited matches) tend to be pretty precise, and have minimal input/output variance. However, as soon as I load a search that has a lot of matches (verified by Count All) and non-trivial chance for false-positives, I'll save my work and restart at the beginning of the doc because a) it'll have been a minute since my last save, given that I was cycling through limited or simple searches, and b) because I'm going to be dealing with a more complex pattern of matches and more of them, it's easier for me to make a mistake and need to backtrack. Regarding (b), if the search hasn't been cycling through files in order and strictly as needed (but rather is cycling from a random starting point, with multiple irrelevant open files), if I erroneously replace a value, it'll be very difficult to go back and find the error if the search has moved to a new file. (The error will have occurred in the last opened file, but that file wouldn't necessarily be the preceding tab if I already had a bunch of files open before I started the search).
Anyway, appreciate you're looking into adding the Refresh shortcut functionality. I'm also going to work on really availing myself of the new Sigil's sequence-tracking. Frankly, it's already a time-saver on the the aforementioned "simple" searches, as it prevents my matching the same strings multiple times after cycling through the document.