Hi Oliver,

> Opened a ZTree Showall Window with a lot of files starting with '0'
> none tagged
> Typed
> match ^0[^0].*
> to select those without second character 0.

That won't work; this script expects exactly match(^0[^0]), including the parentheses, and no extra spaces anywhere.

> Ztree hangs waiting for the script host to finish (with the spinner
> rotating) the script displays:
> regex.js match ^0[^0].*(current file name) >>[Empty]
> but does nothing. This goes on till I type Esc in Ztree.

When it outputs >>[Empty], that means that the script doesn't recognize and acknowledge the command, so ZTreeWin waits indefinitely for a ZAAP, any ZAAP, to respond...

Keep in mind that all ZAAPs get to see the command, so if a ZAAP doesn't recognize the command, I prefer it to ignore it, in case some other ZAAP (or script, in this case) does recognize it. Perhaps I'll add a procedure for each script to register for a specific command, to reduce the potential for conflicts.

> Changing the call to
> match(^0[^0].*) produces the same effect.

That's odd. I just tried match(^0[^0].*), and it correctly tagged the file starting with '0', and untagged all the other files (including the one starting with '00').

Are you certain there isn't some stray space somewhere in the command line? They're not being removed as yet, and the script is rather strict in its recognition of the command.

> Tagging all the files and typing the command with Ctrl-Y causes the
> system to stop at the first tagged file in the same way.

> Obviously I'm doing something wrong - can you clarify please?

When you used the match with parentheses, what did the log window show?