ok. What I often do is record a macro, then stop recording and click the edit button in the dialog to see what got recorded and "steal" some of the code. For replace in files you get something like this
_command last_recorded_macro() name_info(','VSARG2_MARK|VSARG2_REQUIRES_EDITORCTL)
{
_macro('R',1);
_mfreplace2('old_text','new_text','WE*','<Workspace>','*.*','','0','1','0');
}
So you could then just edit the macro (lastmac.e gets opened) and add more calls to _mfreplace2
_mfreplace2('old_text2','new_text2','WE*','<Workspace>','*.*','','0','1','0');
Click load module on the macro menu to load lastmac.e, then click "execute last macro" in the macro menu to run it.
As you can see, slick macro recording records commands rather than keystrokes. If you know a little bit about how to write macros you don't need slick to record keystrokes in the search dialog. If you don't (99% of people), I guess if slick macro recording wanted to be really smart, it could take notice of you "pasting" text into the search or replace string - then maybe adjust the recorded macro after asking if you want the literal text or the "clipboard" contents.
Graeme