Skip to main content
Commonmark migration
Source Link

If you have a command window open and call the commands manually, you can display a timestamp on each prompt, e.g.

prompt $d $t $_$P$G

It gives you something like:

23.03.2009 15:45:50,77

 

C:\>

If you have a small batch script that executes your commands, have an empty line before each command, e.g.

(empty line)

 

myCommand.exe

 

(next empty line)

 

myCommand2.exe

You can calculate the execution time for each command by the time information in the prompt. The best would probably be to pipe the output to a textfile for further analysis:

MyBatchFile.bat > output.txt

If you have a command window open and call the commands manually, you can display a timestamp on each prompt, e.g.

prompt $d $t $_$P$G

It gives you something like:

23.03.2009 15:45:50,77

 

C:\>

If you have a small batch script that executes your commands, have an empty line before each command, e.g.

(empty line)

 

myCommand.exe

 

(next empty line)

 

myCommand2.exe

You can calculate the execution time for each command by the time information in the prompt. The best would probably be to pipe the output to a textfile for further analysis:

MyBatchFile.bat > output.txt

If you have a command window open and call the commands manually, you can display a timestamp on each prompt, e.g.

prompt $d $t $_$P$G

It gives you something like:

23.03.2009 15:45:50,77

C:\>

If you have a small batch script that executes your commands, have an empty line before each command, e.g.

(empty line)

myCommand.exe

(next empty line)

myCommand2.exe

You can calculate the execution time for each command by the time information in the prompt. The best would probably be to pipe the output to a textfile for further analysis:

MyBatchFile.bat > output.txt
Active reading.
Source Link
Peter Mortensen
  • 31.4k
  • 22
  • 110
  • 134

If you have a command window open and call the commands manually, you can display a timestamp on each prompt, e.g.

prompt $d $t $_$P$G

It gives you something like:

23.03.2009 15:45:50,77

C:\>

ifIf you have a small batch script that executes your commands, have an empty line before each command, e.g.

(empty line)

myCommand.exe

(next empty line)

myCommand2.exe

youYou can calculate the execution time for each command by the time infoinformation in the prompt. The best would probably be to pipe the output to a textfile for further analysis:

MyBatchFile.bat >output> output.txt

If you have a command window open and call the commands manually, you can display a timestamp on each prompt, e.g.

prompt $d $t $_$P$G

gives you something like

23.03.2009 15:45:50,77

C:\>

if you have a small batch script that executes your commands, have an empty line before each command, e.g.

(empty line)

myCommand.exe

(next empty line)

myCommand2.exe

you can calculate the execution time for each command by the time info in the prompt. The best would probably be to pipe the output to a textfile for further analysis:

MyBatchFile.bat >output.txt

If you have a command window open and call the commands manually, you can display a timestamp on each prompt, e.g.

prompt $d $t $_$P$G

It gives you something like:

23.03.2009 15:45:50,77

C:\>

If you have a small batch script that executes your commands, have an empty line before each command, e.g.

(empty line)

myCommand.exe

(next empty line)

myCommand2.exe

You can calculate the execution time for each command by the time information in the prompt. The best would probably be to pipe the output to a textfile for further analysis:

MyBatchFile.bat > output.txt
Source Link
Treb
  • 20.3k
  • 8
  • 60
  • 88

If you have a command window open and call the commands manually, you can display a timestamp on each prompt, e.g.

prompt $d $t $_$P$G

gives you something like

23.03.2009 15:45:50,77

C:\>

if you have a small batch script that executes your commands, have an empty line before each command, e.g.

(empty line)

myCommand.exe

(next empty line)

myCommand2.exe

you can calculate the execution time for each command by the time info in the prompt. The best would probably be to pipe the output to a textfile for further analysis:

MyBatchFile.bat >output.txt