_DO_FILES not reset

[vefatica]

This tells me there are 181 files in v:\.

v:\> do f in /a:-d * ( echo foo > NUL) & echo %_do_files
181

V:\num is empty, but

v:\num> do f in /a:-d * ( echo foo > NUL) & echo %_do_files
181

Note that _STARTPID behaves similarly, retaining its last value when START fails (see thread in "Suggestions").

 

[Alpengreis]

Yes, it DOES change if there are more/less files but not if a directory is empty.

 

[rconn]

That would break nested DO's.

 

[vefatica]

Is there anything the user can do to avoid this (besides start a new instance of TCC)?

 

[Alpengreis]

Yes, that would be very interesting for me too! A possibility to avoid that behaviour would be very sensefully while in same TCC session ...