<p><em>Note: Though my original answer attracted several upvotes, I decided that I could do much better. Vous pouvez find my original (simplistic and misguided) answer in the edit history.</em></p>
<p>If Microsoft had the intent of providing a means of outputting a blank line from <code>cmd.exe</code>, Microsoft surely would have documented such a simple operation. It is this omission that motivated me to ask this question.</p>
<p>So, because a means for outputting a blank line from <code>cmd.exe</code> is <em>not</em> documented, arguably one should consider any suggestion for how to accomplish this to be a <em>hack</em>. That means that il y a no known method for outputting a blank line from <code>cmd.exe</code> that is <em>guaranteed</em> to work (or work efficiently) in <em>all</em> situations.</p>
<p>With that in mind, here is a discussion of methods that have been recommended for outputting a blank line from <code>cmd.exe</code>. All recommendations are based on variations of the <code>echo</code> command.</p>
<p>echo.</p>
<pre><code class="lang-auto">
While this will work in many if not most situations, ***it should be avoided*** because it is slower than its alternatives and actually can fail (see [here](https://stackoverflow.com/a/6379940/1497596), [here](https://stackoverflow.com/a/20691856/1497596), and [here](http://www.dostips.com/DtCodeSnippets.php#Snippets.EchoEmptyLine)). Specifically,cmd.exefirst searches for a file namedechoand tries to start it. If a file namedechohappens to exist in the current working directory,echo.` will fail with:
`'echo.' is not recognized as an internal or external command,
operable program or batch file.
</code></pre>
<p>echo:<br>
echo\</p>
<pre><code class="lang-auto">
At the end of [this answer](https://stackoverflow.com/a/6379940/1497596), the author argues that these commands can be slow, for instance if they are executed from a network drive location. A specific reason for the potential slowness is not given. But one can infer that it may have something to do with accessing the file system. (Perhaps because:and` have special meaning in a Windows file system path?)
However, some m
(Réponse tronquée)</code></pre>
