DosTips.com

Edit: sorry, overlooked the intent with the timeout tied to the key detection interrupt. Seems indeed any 'w' input from a command to the right of the timeout pipe is eaten, even if handled with something else like Powershell. Prior post below, edited a little: --- There's a Powershell way to detect...

It stuns me the hurdles to just running Powershell scripts. It's easier to run both a binary or batch script that launches Powershell than PS per se, which seems counter-intuitive if their goal was to encourage it as a replacement but I'm probably veering off-topic.

But how can I effectively use Binit also outside of a BAT script, i.e. incorporate it to a daily and on the spot usage? You'd use it like any CLI program. I mean, that's what you're doing in the OP. I would have to write and always be running e.g. AHK script that would replace pressing of Delete ke...

There's a CLI program called binit that sends things to the recycle bin. In my testing it handled all the Unicode characters I tried, unlike another program (CmdUtils) that I'd seen suggested elsewhere. Not open source fwiw. The author posted their motivation for creating it on Stack Overflow.

Based on the OP it sounds like you only want a copy of the singular 'build.a' file in the name of the 'Build_...' directory name, within a sibling top-level 'Result' directory. In which case the following works. Simply have the parent directory as the input of the script (eg: by dragging the directo...

There's a utility called byenow from the dev of Bvckup that is faster (some bechmarks of byenow/del/rmdir/robocopy appear on the page). May want to test it.

Edit: forgot it takes directories as inputs only.

Fwiw 7-Zip, which has a useful and easy-to-use CLI binary, still supports XP according to their home page.

%0 is the full path of the script Nope. %0 contains how the script was called. Consider to have a "FOO.bat". From within a command prompt you could just enter FOO to run it. But in this case %0 expands to only FOO where deleting would fail. To expand it to the full path you have to use "%~f0" (incl...

Looks neat. Glad for the video. Some threads that aren't even particularly old have been affected by changes to image hosts, both with Photobucket changing their hotlinking terms and Tinypic ending which leads to many broken images but I'd imagine YT will stick around a bit.

Hi, At that time I had simply forgotten an endlocal which I had now inserted. Therefore, the pairs should always be turned on and off exactly. Very interesting. Quite a bit over my head :) Would someone mind explaining in which part the variables could be set for use under enableddelayedexpansion e...

There's still something wrong in you current version. The first argument consists of several paths. Updated both scripts. It now divides the input paths into new lines within the single arguments variable, then wraps each line in double quotes regardless of whether the path has spaces or not. The p...

Interesting! I'll keep that in mind. There's still something wrong in you current version. The first argument consists of several paths. Oops, must have been I tested the double quote pre-wrapping manipulation with a certain selection of those inputs that didn't reveal this mistake (I've also found...

Yes, unfortunately. The problem you are facing is still caused by the ampersand bug. If you drag/drop a file with the name you provided to a script that consists of nothing but @pause , the cmd will still crash. You don't even have any chance to access the cmdcmdline variable. Updated the scripts t...

Updated two lines to differently trim the args variable so it works properly for paths with ampersands and no spaces (a test I forgot to try until I was reminded of it by this topic). Edit: ampersands and alphanumeric by themselves are fine however after testing a path with no spaces with !§$%&()=`´...

Yes, I got these as well when I tried posting a message about my updated version of which.exe last week. Looks like it's working without errors currently, so hopefully it's sorted :) In the meantime realized I hadn't accounted for paths without spaces in the initial 'new method' scripts (which obvi...