Monster JPSTREE.IDX, maybe? Does adding /N to MD / RD help?

Vince, do you by any chance have "Delete to Recycle Bin" enabled? It's under OPTION / Startup.

I had 3,128 on my laptop at home. RD /S in a FOR loop removed them all in about 4½ seconds. I think something must be going on with your system.

FOR does support wildcards. You should be able to nuke them with something like: for /d %dir in ( C:\Windows\System32\config\systemprofile\AppData\Local\tw-* ) do rd /s /q "%dir" Maybe insert an ECHO between the DO and RD to test, first.

Perhaps F7, End is closer to what you want?

I just tried the experiment, and I can reproduce this in the current v36. It looks like /IP must precede any of the other /Ix options on the command line: start /pgm %_cmdspec /ip disables automatic loading of plugins, but start /pgm %_cmdspec /il /ip does load plugins. I would say that this...

«slaps forehead» That explains a lot. I never would have thought of FUNCTION being aliased, but in retrospect it makes sense. Thank you.

I don't think it supports the suffix. 512K would be 524288, but that's huge. I don't have a FunctionSize directive, and TCC defaults to 32768. That's plenty for me. I'm completely at sea as to how that command line could not define a function. It feels as if quoting is disabled, but that's...

I don't see anything weird there.

I'm having a hard time imagining what could possibly cause this. If you type SETDOS by itself, do you see anything peculiar? In particular, "Expansion" should be zero, and "Parameters" should be the dollar sign.

Looks like it never got properly added to the .CHM file, for one thing. Handling of negative values is a little peculiar. If you try to go back past the beginning of the file, it returns the first line. This happens even if you specify /E and the first line is blank. Didn't seem worth fixing...

Perhaps the regex engine has some expression to match whitespace characters in general, instead of just tabs?

That "Incorrect function" error suggests to me that the function is not being defined. You might try function leftmost function tomorrow (no equals signs, no definitions) to see what, if anything, is getting stored.

You're forgetting the strong quotes around the function definition: C:\>function leftmost=`%@left[1,%1]` C:\>echo %@leftmost[xyz] x C:\> Without the quotes, all that stuff to the right of the equals sign is evaluated before the function is defined. And what it evaluates to is nothing, so...

I can replicate this. Doing something time-consuming, like dir /a /s c:\windows\system32\, reports 0.000 when the command exits normally. But, if I use Ctrl-C to abort, I do see a reasonable value.