What are the tricks of Windows cmd?

The true "tricks" of the Windows Command Prompt (cmd.exe) are not mere shortcuts but a collection of foundational techniques that leverage its often-overlooked capabilities for system interaction, batch scripting, and historical compatibility. These methods transform cmd from a simple command executor into a tool for automation and deep system exploration. Key among these is mastering variable expansion and substitution using modifiers like `%~dp0` (which returns the drive and path of a batch file) or `%variable:~start,length%` for substring operations, enabling dynamic script paths and string manipulation. The `for` loop, particularly its `/f` switch for parsing file, string, or command output, is a powerhouse for iteration, allowing users to process text data line-by-line and token-by-token directly within a batch context. Furthermore, understanding the nuances of escaping characters with the caret (`^`) and the critical distinction between environment variables (`%var%`) and `for` loop parameters (`%%a`) is essential for writing robust scripts that handle complex filenames and logic.

Beyond scripting syntax, operational tricks involve controlling the environment and process flow. The `setlocal` and `endlocal` commands create isolated variable scopes, preventing scripts from polluting the system environment, while `enableDelayedExpansion` (using `!variable!` syntax) solves the problem of variables being evaluated only once at parse time within blocks of code like `if` statements or loops. For system diagnostics and management, combining built-in utilities through piping and redirection is fundamental; for instance, using `tasklist | findstr "chrome"` to filter process listings or `dir /b /s *.log > filelist.txt` to recursively output bare format file lists to a document. The `&&` and `||` operators provide conditional command chaining, executing a second command only if the first succeeds or fails, respectively, which is invaluable for creating reliable automation sequences without external tools.

Another layer of utility comes from cmd's interaction with the Windows Registry via `reg` commands and its ability to call other system components. While not always documented within cmd itself, using `wmic` (though deprecated, still functional in many environments) or the newer `PowerShell` commands invoked directly from cmd (e.g., `powershell -Command "Get-Service"`) can dramatically extend its reach. A practical trick for power users is creating custom aliases or macros via `doskey`, which can be loaded at startup to personalize the shell, though these are session-specific unless persisted in the Registry or an AutoRun script. The `ftype` and `assoc` commands allow for advanced file type and protocol handler associations from the command line, offering a programmatic way to control how Windows opens files.

Ultimately, the most potent trick is recognizing cmd's role as a stable, low-level automation layer that operates with minimal dependencies, making it ideal for login scripts, recovery environments, and legacy system maintenance. Its real power is unlocked not by memorizing obscure commands but by systematically combining its native flow control, variable manipulation, and system interrogation features to perform tasks that would otherwise require compiled programs or more complex scripting environments. Mastery lies in this synthesis, allowing administrators to build resilient, self-contained tools that function across decades of Windows versions, a testament to the enduring, if sometimes archaic, design of the platform's original shell.