| 2006-11-03 14:03:53 |
John A Meinel |
description |
If you run the native windows client inside a cygwin prompt then the bzr break-lock command appears to hang. This is because the user does not see any output on the terminal and does not realise they are being asked a question that they need to respond to. This may be the case with other interactive commands too. Running it inside a DOS prompt the user sees the question bzr is asking and so there is no problem.
Note that in general output seems to be displayed on the terminal even inside a cygwin prompt. It only seems to be when the user is prompted for input that the question is not displayed. Could this be due to different flush policies in cygwin and dos prompt? Perhaps Cygwin only flushes output when a \n character is output. |
If you run the native windows client inside a cygwin prompt using rxvt or gnome-terminal, then the bzr break-lock command appears to hang. This is because the user does not see any output on the terminal and does not realise they are being asked a question that they need to respond to. This may be the case with other interactive commands too. Running it inside a DOS prompt the user sees the question bzr is asking and so there is no problem.
Note that in general output seems to be displayed on the terminal even inside a cygwin prompt. It only seems to be when the user is prompted for input that the question is not displayed. Could this be due to different flush policies in cygwin and dos prompt? Perhaps Cygwin only flushes output when a \n character is output. |
|
