public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] cygwin 3.1.0-0.6 (TEST)
Date: Fri, 18 Oct 2019 11:36:00 -0000	[thread overview]
Message-ID: <20191018203632.f05b8bf99cb7d3ac384b1d99@nifty.ne.jp> (raw)
In-Reply-To: <20191016213255.00a144f60395eb00c9ba5f3b@nifty.ne.jp>

Hi Michael,

On Wed, 16 Oct 2019 21:32:55 +0900
Takashi Yano wrote:
> On Mon, 14 Oct 2019 13:07:22 +0200
> Michael Haubenwallner wrote:
> > Actually I do prefer the TERM=dumb behaviour, having the current terminal
> > buffer content get redrawn at line 1 when cmd is started only, not when
> > running just Cygwin programs.
> > 
> > My real problem is more sophisticated, and boils down to the creation of some
> > pty's in a row, each having some commands run inside, and I do expect to see
> > the output of each command while the series runs and when done, much like:
> > 
> > ----------------------------------------
> > > {some output from previous linux commands}
> > > {some output}
> > > {some output}
> > > haubi@linuxbox ~ $ ssh -t cygwin2016 hostname; hostname; ssh -t cygwin2016 hostname
> > > cygwin2016
> > > Connection to cygwin2016 closed.
> > > linuxbox
> > > cygwin2016
> > > Connection to cygwin2016 closed.
> > > haubi@linuxbox ~ $
> > ----------------------------------------
> 
> Let me consider...

I have made a patch for this dilemma and will submit soon.
Could you please test?

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

--
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:[~2019-10-18 11:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-22 16:24 Ken Brown
2019-09-24  7:38 ` Michael Haubenwallner
2019-09-24 12:50   ` Ken Brown
2019-09-24 23:05 ` Ken Brown
2019-09-25 18:30   ` Takashi Yano
2019-09-26 12:51     ` Takashi Yano
2019-09-26 14:38       ` Ken Brown
2019-10-02 14:04 ` Michael Haubenwallner
2019-10-02 18:24   ` Ken Brown
2019-10-03 10:44   ` Takashi Yano
2019-10-10 10:44 ` Michael Haubenwallner
2019-10-11  9:25   ` Takashi Yano
2019-10-14 11:07     ` Michael Haubenwallner
2019-10-16 12:32       ` Takashi Yano
2019-10-18 11:36         ` Takashi Yano [this message]
2019-10-16 14:34       ` Takashi Yano
2019-10-16 16:34         ` Michael Haubenwallner

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=20191018203632.f05b8bf99cb7d3ac384b1d99@nifty.ne.jp \
    --to=takashi.yano@nifty.ne.jp \
    --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).