* The bash console exits in 2.9.0
@ 2017-09-10 11:36 Nick Popoff
2017-09-10 12:24 ` Achim Gratz
0 siblings, 1 reply; 4+ messages in thread
From: Nick Popoff @ 2017-09-10 11:36 UTC (permalink / raw)
To: cygwin
Maybe, you are already aware of this problem introduced in 2.9.0. When I
say, for example:
man ls
The bash console just exits and 'less' stays running in memory until I kill
it. This behavior completely disrupted everything I was doing. The scripts
are with the same behavior seemingly when '&' is used to put the command in
background. Thanks God, I had backups and restored 2.8.2.
Nick
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: The bash console exits in 2.9.0
2017-09-10 11:36 The bash console exits in 2.9.0 Nick Popoff
@ 2017-09-10 12:24 ` Achim Gratz
2017-09-10 14:07 ` Marco Atzeri
2017-09-12 15:56 ` Houder
0 siblings, 2 replies; 4+ messages in thread
From: Achim Gratz @ 2017-09-10 12:24 UTC (permalink / raw)
To: cygwin
Nick Popoff writes:
> Maybe, you are already aware of this problem introduced in 2.9.0. When I
> say, for example:
>
> man ls
>
> The bash console just exits and 'less' stays running in memory until I kill
> it. This behavior completely disrupted everything I was doing. The scripts
> are with the same behavior seemingly when '&' is used to put the command in
> background. Thanks God, I had backups and restored 2.8.2.
More specifically, this happens for programs started from a console
window (cmd), but not when the same commands are run in mintty (the
shell itself doesn't seem to have anything to do with it).
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: The bash console exits in 2.9.0
2017-09-10 12:24 ` Achim Gratz
@ 2017-09-10 14:07 ` Marco Atzeri
2017-09-12 15:56 ` Houder
1 sibling, 0 replies; 4+ messages in thread
From: Marco Atzeri @ 2017-09-10 14:07 UTC (permalink / raw)
To: cygwin
On 10/09/2017 14:24, Achim Gratz wrote:
> Nick Popoff writes:
>> Maybe, you are already aware of this problem introduced in 2.9.0. When I
>> say, for example:
>>
>> man ls
>>
>> The bash console just exits and 'less' stays running in memory until I kill
>> it. This behavior completely disrupted everything I was doing. The scripts
>> are with the same behavior seemingly when '&' is used to put the command in
>> background. Thanks God, I had backups and restored 2.8.2.
>
> More specifically, this happens for programs started from a console
> window (cmd), but not when the same commands are run in mintty (the
> shell itself doesn't seem to have anything to do with it).
>
tested with cygwin.bat 32 and 64 on W7-64
The effect seems present only the first time that cygwin.bat is run;
the processes remains frozen but a second run seems to work fine.
So may be is a run issue on the first invocation.
Regards
Marco
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: The bash console exits in 2.9.0
2017-09-10 12:24 ` Achim Gratz
2017-09-10 14:07 ` Marco Atzeri
@ 2017-09-12 15:56 ` Houder
1 sibling, 0 replies; 4+ messages in thread
From: Houder @ 2017-09-12 15:56 UTC (permalink / raw)
To: cygwin
On Sun, 10 Sep 2017 14:24:00, Achim Gratz wrote:
> Nick Popoff writes:
> > Maybe, you are already aware of this problem introduced in 2.9.0. When I
> > say, for example:
> >
> > man ls
> >
> > The bash console just exits and 'less' stays running in memory until I kill
> > it. This behavior completely disrupted everything I was doing. The scripts
> > are with the same behavior seemingly when '&' is used to put the command in
> > background. Thanks God, I had backups and restored 2.8.2.
>
> More specifically, this happens for programs started from a console
> window (cmd), but not when the same commands are run in mintty (the
> shell itself doesn't seem to have anything to do with it).
Perhaps this script will help in finding the bug ...
- 2.9.0: "console is lost"
- 2.8.2: ... works
Regards,
Henri
(P.S. modifying /usr/bin/nroff accordingly will not make 'man ls' operate as
desired)
-----
#! /bin/sh
# invoke like this: cat strange.sh | ./strange.sh
#case "`exec 2>/dev/null ; locale charmap`" in # as used in /usr/bin/nroff
case "`locale charmap`" in # ... works
UTF-8) echo utf-8 ;;
*) echo none ;;
esac
echo Tada
-----
#=====
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2017-09-12 15:56 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-09-10 11:36 The bash console exits in 2.9.0 Nick Popoff
2017-09-10 12:24 ` Achim Gratz
2017-09-10 14:07 ` Marco Atzeri
2017-09-12 15:56 ` Houder
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).