--- In [email protected], sgp <[EMAIL PROTECTED]> wrote: > Hi Sheri, it's a nice script and a good example of the power of > regex 2 plugin.
Thanks. Just looked at it and noticed a potential problem. You should move down the label @pasthVec to below the two regular expressions that currently follow it. In other words, the next line after that label should be the comment that starts ;put a space > I noticed you have "else do" - I don't think "do" is necessary or > possibly even legal. Now that you mention it, I don't see "else do" documented anywhere, but it must work, because a quick search of my scripts directory shows that I used it in most of my scripts. > The script leaves all comments in place > except inline ;; comments, right? Have you tried what happens > with block style /* */ comments? That's correct. Just tested block style comments. They do not work in command-line based scripts. And there is another marker for anywhere-on-the-line comments besides ;;. It is // Those also don't work. But // is legitimate as part of urls and other command content, so I'm not sure if I can do anything with that. Block-style comments I could probably remove easily (even multiline). Guess you use them, huh? It would be nice if I could detect whether any of these makers were inside quotations or pp literals, because anything would be legitimate as part of a quoted string. But I don't think that would be easily done. Regards, Sheri
