I don't know why you would want to call i-search from a macro though, if you already know what text you're searching for.
Let me give you another example for how this is very powerful. Lets say I have a .csv file containing rows from a database:
1,"Joe", "Shmoe", "225 Some Rd", "Some City", "NY", "10028"
2,"Jean", "McGoogle", "1 First St NW", "Some Other City", "CA", "91112"
etc....
Now, lets say I want to copy only the
cities from my data. I can record a disposable macro which:
1) searches for the correct quote (the 7th);
2) begins a selection on the next character;
3) does another search for the next quote;
4) then copies the selection somewhere else.
I can then repeat this macro I just recorded in a few seconds on every line. Voila! I have my list of cities.
I understand that I could do this programatically, or "why the h*ll didn't I just do 'select city from table' in the first place?", but my point is that there is a good reason I found myself using this feature constantly in CodeWright in "throw-away" macros like the example above.
By the way, I am absolutely loving SE, have about 1000 lines of new macros coded up in the first week of my switch from CodeWright, and (other than this little bump) am doing everything I could do in CW and more!
Great job.