mysql command line client hangs in cygwin xterm
Wed Apr 28 03:02:00 GMT 2004
On Wed, Apr 28, 2004 at 10:47:59AM +1000, Richard Piper wrote:
>The problem seems to be well described in the general cygwin mailing
>list. As yet I have not seen a solution.
Yeah, that was an interesting email. It was nice to see that someone
agreed with my assessment of the problem. It is always a relief to hear
that I do know what I'm talking about from people who don't quite know
what they are talking about.
As I mentioned, the easiest solution is to always use cygwin built
programs if you want to run a program on a cygwin pty.
The logic that there had to be a solution to this problem because it
affects so many programs did escape me, though. I'd be very happy to
see someone find a way to fool programs into thinking they are running
on a console when they are using a cygwin pty but the fact that it is a
serious problem doesn't mean that there is automatically going to be a
solution to the problem.
>"Richard Piper" <rpiper <at> med.usyd.edu.au> wrote in message
>>This seems to hang in the cygwin xterm. Has anyone seen this problem?
>>Seems to work normally in the xterm on other systems and at the NT
>I've seen other applications work in a command shell but not rxvt. I
>assume you're having the same problem with xterm. Basically, the output
>isn't getting flushed out so you can't see it, but whatever you type is
>still accepted as input.
>Sorry, don't know of any way to fix it, other than sticking with cmd.exe.
>Maybe you can have an alias that will pop-up a regular cygwin window (in a
>command shell) for when you want to use mysql, and you can stick to xterm
>for the rest of your stuff.
>Note that this problem is a problem with cygwin and not anything in
>cygwin/x specifically. That's why rxvt has the same problem, whether you
>run it in native windows mode or X mode. So, if you want more information
>on it, I suggest asking in the regular cygwin mailing list.
More information about the Cygwin-xfree