This question already has an answer here:

I have a few python scripts which contain no pause commands and no prompts for user input however I find that when I change my window focus to the Windows cmd window the output will freeze until I press 'Enter'.

Is there a know cause for this? Should I enable/disable a setting in the cmd options to avoid this?

A search of my case keeps bringing up cases of people wanting pauses in their code - which I do not.

marked as duplicate by Pimp Juice IT, music2myear, G-Man, djsmiley2k, James P Oct 24 '17 at 13:24

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

up vote 21 down vote accepted

How are you selecting/focussing that window? If you simply Alt+Tab to it or click its titlebar, the scrolling output shouldn't pause. My guess is you have QuickEdit Mode turned on (right-click the command prompt windows's titlebar and select Properties) and you are clicking inside the window with your mouse, thus selecting text by mistake and causing the program to pause.

1

  • Thanks Karan. Yes I was using QuickEdit to select some text from the output of my scripts. Disabling this gets around the pausing. Shame the cmd window can't let you select text without pausing the output. – Markus Feb 22 '13 at 0:34
  • Don't you think it would be difficult to select text that's quickly scrolling off the screen? – Karan Feb 22 '13 at 0:41
  • I guess it depends on how "quickly" it is scrolling off the screen. – Markus Feb 24 '13 at 23:50
  • 1
    The reasoning to make it freeze is likely dictated by some old software limitation(s), not because it's convenient for the user. Modern apps would have its process continue down below the selection and show a scrollbar. – LessQuesar Apr 29 '14 at 21:38
  • 1
    And it's awesome that Windows doesn't provide an easy way to prevent an individual batch script's cmd from having this option enabled without doing something 'hacky'...it's kind of silly how Windows presents you the options of trusting the end user to disable this option in their cmd, doing something 'hacky', or implementing your own GUI to send stdout/err to in order to display without this issue. – searchengine27 Oct 21 '16 at 20:04

Not the answer you're looking for? Browse other questions tagged or ask your own question.