I've been having this odd issue recently where my command line screens will basically lock the programs writing to them until I give mouse focus to the DOS window and then perform some keyboard action.

So, for example: I'll start a Tomcat instance and at some point, it simply stops updating -- I hit reload and nothing happens, nothing outputs to the Catalina window. Or, I'll check out something from SVN and it will appear to lag, but as soon as I interact with it, the lag stops.


My aplogies, I used the word "screen" when I meant "window" (that is fixed).

The command (to start Tomcat):


The command to checkout a repository (in Cygwin):

$ svn checkout <repository>

To the requests to change the operating system, I say "no". At no point have I mentioned which operating system I was using, I simply stated that I was using DOS (common use implies MS, but the comments stated that I have incorrectly stated which OS I was using). Since this problem has never exhibited itself in anything other than that environment, it is not intuitive to say that this is a Windows problem.

  • "Focus on the screen": This isn't DOS. What operating system is it? – JdeBP Jun 15 '11 at 18:58
  • You are not running Tomcat under DOS. Edit your question to state your real operating system and real software including versions for your terminal emulator and shell. – CarlF Jun 15 '11 at 19:02
  • Do you start this program from the command line, shortcut, or some other way? If from the command line or shortcut, please post this info. – jftuga Jun 15 '11 at 19:02

As far as I know, when you selecting text in a in a command-prompt/console windows, the console application will be "locked" until your selection is done (press ENTER) or canceled (press any key else).

If QuickEdit mode of a command prompt window is ON, you'll probably enter selecting text state by a single mouse click in the client area of command prompt window. This is a misoperation often occured if QuickEdit mode is ON.

If you're in the above situation, you can simply turn QuickEdit mode OFF to avoid this misoperation.

  • 1
    These are not "DOS prompt" windows. And you've assumed something not in the question, that the rest of us have instead asked to be supplied. – JdeBP Jun 15 '11 at 19:33
  • @JdeBP Actually, they are. While you may not like the reference, the common name for the cmd.exe program is "DOS prompt" (especially since MS commonly refers to it as such). I'll give you that Cygwin is not exactly the same thing, but since I've no idea what to call it, I used the closest approximation. – cwallenpoole Jun 15 '11 at 19:47
  • 1
    You are conflating common with incorrect. No, Microsoft does not make this error, contrary to your claim. It fixed the nomenclature used on the Explorer desktop years ago in Windows NT 5, as noted. Calling these things "DOS prompts" is just plain wrong any way one slices it. They are Windows NT console windows. And CMD is nothing to do with DOS at all, as I, Tim Hill, and many other people explain. Learn that this is an outright error that you are propounding. – JdeBP Jun 15 '11 at 21:00
  • 1
    @JdeBP Thanks for the correction of my misnomer. Assuming something instead of asking to be supplied is a different way of working, it's unprofessional, but it's working. Anyway, I just want to help. – LiuYan 刘研 Jun 16 '11 at 3:13

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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