public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: The bash console exits in 2.9.0
Date: Tue, 12 Sep 2017 15:56:00 -0000	[thread overview]
Message-ID: <2642aaf3c77276a3eb2c9fef82d128bc@smtp-cloud8.xs4all.net> (raw)
In-Reply-To: <87tw0aivxb.fsf@Rainer.invalid>

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

      parent reply	other threads:[~2017-09-12 15:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-10 11:36 Nick Popoff
2017-09-10 12:24 ` Achim Gratz
2017-09-10 14:07   ` Marco Atzeri
2017-09-12 15:56   ` Houder [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2642aaf3c77276a3eb2c9fef82d128bc@smtp-cloud8.xs4all.net \
    --to=houder@xs4all.nl \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).