public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@yandex.ru>
To: Jim Reisert AD1C <jjreisert@alum.mit.edu>, cygwin@cygwin.com
Subject: Re: Bash shell inside JPSOFT Take Command does not respond to input
Date: Mon, 15 May 2017 05:30:00 -0000	[thread overview]
Message-ID: <588565953.20170515052912@yandex.ru> (raw)
In-Reply-To: <CAK-n8j4nknb1nv4i03uaT8csty5o3v8rGJr-Fk7-HYkGKBMEYw@mail.gmail.com>

Greetings, Jim Reisert AD1C!

> I can't seem to get a bash shell to run inside of JP Software's Take Command:

>    www.jpsoft.com

They have their own support forum, BTW.

> Behavior is the same in both TC and TCC - a shell starts, but I can't
> type anything into it.  This used to work in the recent past, so I
> don't know what changed, or when.  Both versions 20 and 21 of the
> JPSOFT product behave the same way:


> TCC  20.11.46 x64   Windows 10 [Version 6.3.16193]
> TCC Build 46   Windows 10 Build 16193
> Registered to JJR

> f:\>bash
> CYGWIN_NT-10.0 JJR 2.8.0(0.309/5/3) 2017-04-01 20:47 x86_64 Cygwin

What about explicit bash -i ?

> [JJR:/cygdrive/f] $  <<< at this point, nothing is echoed, nothing is accepted

Can't confirm with TCC RT 21 and LCC/LE 14.


-- 
With best regards,
Andrey Repin
Monday, May 15, 2017 05:27:13

Sorry for my terrible english...


--
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

  reply	other threads:[~2017-05-15  2:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-15  1:59 Jim Reisert AD1C
2017-05-15  5:30 ` Andrey Repin [this message]
2017-05-15 12:55 ` Brian Inglis
2017-06-25 10:05   ` Jim Reisert AD1C

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=588565953.20170515052912@yandex.ru \
    --to=anrdaemon@yandex.ru \
    --cc=cygwin@cygwin.com \
    --cc=jjreisert@alum.mit.edu \
    /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).