I copy-pasted the line and did not see that the \ were removed for some
reason. The 1,2,3 all have \ of cause.
:%s/expectedMessage =&(\(\(.*\) *\)\(.*\);/CsrMemCpy(expectedMessage,
\&((1 *) 2, sizeof(1));/
Mmm. Well, it still could be to do with the pattern. That one above can
certainly match multiple ways, which get larger even faster than
exponentially in some cases, which would grind things to a halt and
easily recurse too far. But that's pattern matching recursion, not
ex-command recursion, so I'm still not convinced it's the problem.
If you gave an exact extract of some of the text you were matching and
how you were expecting it to be transformed, we could at least check the
pattern. And that would be a start I guess.
If this is even still relevant at all, given how much time has passed,
and you haven't just resorted to doing it manually or with another
script or something. :-)
Ben.
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
