DosTips.com

@echo off Don't show the prompt and don't repeat the command. setlocal Not necessary. Just one of my defaults to avoid variables to be predefined if I run scripts from a cmd prompt for debugging reasons. for /f "delims=" %%i in FOR /F processes streams line by line. It usually devides a line into t...

You're about making it an XY problem. Neither do you need to write a text file, nor do you ever need to know the number of files. Just process the output of DIR directly, preferably with a filter that excludes file names containing "4sec". Give that a go: @echo off &setlocal for /f "delims=" %%i in ...

I found some time to dig a little deeper ... As much as I agree with Arthur Clarke, things are often not that obvious. Especially in highly abstracted languages where you don't know how much complexity is hidden in the implementation of a simple command such like REM, where we already know that it i...

Even if you don't find anything about it in the internet, it'd be so easy to figure it out. You know where the values are saved in the registry. So, just change the compatibility in the context menu of the executable and observe the updated registry value. Press F5 to reload the regedit interface. S...

The console window has no such limits. It's always the command line tool or shell that either spawned the console or is waiting and consuming the input that you enter. All we can do is guessing though. If the console can't be the culprit... The cmd shell has other limits and it would be unlikely tha...

After reading jfl's timing of the NOP macro, I think we should probably go back to an IF statement. for /f %%! in ("! ^! ^^^!") do ^ set ThisMacro=for %%. in (1 2) do if %%.==2 (%\n% for /f "tokens=2" %%1 in ("%%!%%! 1 0") do (%\n% if 1==%%1 setlocal EnableDelayedExpansion%\n% echo(%%!Args_ThisMacro...

Uhh that's something that can drive you mad. You need to glue it to the next command because it would be treated as a separate command otherwise. Even an empty string or a space is parsed like that. I can't make my brain remember the order and details of script parsing. However, you may find the ans...

To REM or not to REM that is the question %%~? for /f %%! in ("! ^! ^^^!") do ^ set ThisMacro=for %%. in (1 2) do if %%.==2 (%\n% for /f "tokens=2" %%? in ("%%!%%! "" rem=") do (%\n% %%~?setlocal EnableDelayedExpansion%\n% echo(%%!Args_ThisMacro:~1%%!%\n% %%~?endlocal%\n% )%\n% ) else set Args_ThisM...

OK, got you. setlocal DisableDelayedExpansion set setfont=for /l %%# in (1 1 2) do if %%#==2 (^ %=% for /f "tokens=1-3*" %%- in ("? ^^!arg^^!") do endlocal^&powershell.exe -nop -ep Bypass -c ^"Add-Type '^ %===% using System;^ %===% using System.Runtime.InteropServices;^ %===% [StructLayout(LayoutKin...

PS:There is a little bug in setting the fonts and I hope that aGerman or someone else will help me solve it I don't get what bug you're talking about. Seems to work on my Win11. (only in Conhost of course, not in Windows Terminal as setting the font programmatically is just not foreseen and will pr...

tl;dr Yes it's worth learning PS. I think we all have some reasons why we decided to do Batch scripting. For some of us just historical reasons like because we grew up with Batch, we are used to write Batch scripts, we are more experienced with Batch than with other scripting languages, we know how ...

It's not VBS. It only uses the COM object WScript.Shell which is one out of many that can be instantiated in VBS but not only in VBS. I doubt that they are going to remove COM objects in the near future. FWIW: MS is telling us that they are about to get rid of VBScript while I've not seen anything a...

JScript hybrid @if (0)==(0) echo off &setlocal &: Batch/JScript hybrid line :: Batch part: :: That's command to run the script file as JScript again. set ^"playsound=cscript.exe //nologo //e:jscript "%~fs0" ^" :: Recursive check where directories (-d) and system files (-s) are excluded. Typically de...

PowerShell is a little off-topic here. However, I had a look at it and found that this behavior is unrelated to PowerShell and happens in Batch as well. It's by design, at least as long as you're running the shell in conhost. Windows Terminal does not override mouse scrolling. If you really want to ...

The only remaining bug related to timeout.exe that I know of is one of a couple "DefTerm" bugs caused by the Windows Terminal set the default terminal host. https://github.com/microsoft/terminal/issues/14499 However, that's probably not the case here because the timeout command would have always ret...