Thank you! That does the trick as long as I'm not too fast between my ctrl-k and ctrl-y.
I think the option to disable the local clipboard for a macro would be handy, then I could go back to writing ctrl-k in the obvious way.
Here's another little gotcha to remember that caught me, that I bet is not obvious to other programmers. When you record a macro that calls a command (or another macro), you might expect that the command/macro would be called, by name, like a function call in a program... However, what really happens is the contents of the command/macro get inserted into the macro you are recording. So, when I changed out the contents of my command that puts the selected text on the clipboard I also had to go back and re-record the macro that calls it.
Could I avoid this if I edit the macro directly? Not sure how to call another command or macro from a macro.
Thanks for your help!
Brad
On Jan 19, 2005, at 4:16 AM, Allan Odgaard wrote:
On Jan 19, 2005, at 11:10, Allan Odgaard wrote:
I admit, it's not very elegant...
I may add an option to disable local clipboard on a per macro basis in b3 or b4, since I think this feature is probably too often the culprit of end-user customization.
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
Brad Miller, PhD Assistant Professor Luther College http://www.cs.luther.edu/~bmiller jabber: bnmnetp@jabber.org