Mail Archives: cygwin/2000/10/31/08:09:35
I have found in the mailing-list archive a workaround for this problem:
>I've seen something that may be the same running cygwin 1.1.4 on
>both WinNT 4 and Win98. If I start an
>external program and fork it from the shell, i.e:
> gvim.exe &
>
>, and then exit gvim, bash eats up the CPU until I hit return at the
>prompt to allow the
> "[1]+ Done gvim"
>message to print. After the message is shown, things seem to run
>ok, but bash does eat up the CPU until the message is printed
The suggested workaround until the problem will be fixed wasthe following:
>Set the "notify" option in BASH (i.e., issue the command "set -o
>notify"). That way BASH prints jobs status changes when they occur,
>instead of waiting for the next time it prints a prompt.
Ok, i have added to my .bashrc "set -o notify" but nothing happens,
means the problem still remains.
Any ideas? In which version of bash this bug will be fixed?
Many thanks in advanve,
Klaus
--
Klaus Berndl mailto: klaus DOT berndl AT sdm DOT de
sd&m AG http://www.sdm.de
software design & management
Thomas-Dehler-Str. 27, 81737 München, Germany
Tel +49 89 63812-392, Fax -220
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
- Raw text -