When running windows native version inside non-standard terminal, bzr appears to hang
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Medium
|
Unassigned |
Bug Description
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.
Changed in bzr: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in bzr: | |
status: | Won't Fix → Fix Released |
Nicholas Allen пишет:
> Public bug reported:
>
> 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.
I cannot reproduce this bug in cygwin bash shell + standalone bzr.exe
0.12 installed. Break-lock command works OK in this combination.
--
Alexander