On Mon, Jun 17, 2013 at 09:58:35AM -0400, Christopher Faylor wrote:
>On Mon, Jun 17, 2013 at 06:08:27AM -0400, Andrew Schulman wrote:
>>> > Do we have any idea whether the problem is with mintty or with screen?
>>>
>>> I observed the same behaviour as the OP, but also reproduced it in
>>> rxvt and
> On Mon, Jun 17, 2013 at 06:08:27AM -0400, Andrew Schulman wrote:
> >> > Do we have any idea whether the problem is with mintty or with screen?
> >>
> >> I observed the same behaviour as the OP, but also reproduced it in
> >> rxvt and xterm, so not a mintty issue. Since it works in a console,
> >
On Mon, Jun 17, 2013 at 06:08:27AM -0400, Andrew Schulman wrote:
>> > Do we have any idea whether the problem is with mintty or with screen?
>>
>> I observed the same behaviour as the OP, but also reproduced it in
>> rxvt and xterm, so not a mintty issue. Since it works in a console,
>> the Cygwin
> > Do we have any idea whether the problem is with mintty or with screen?
>
> I observed the same behaviour as the OP, but also reproduced it in
> rxvt and xterm, so not a mintty issue. Since it works in a console,
> the Cygwin pty layer has to be the main suspect, unless screen has
> specfic cod
On Jun 14 12:57, Andy Koppe wrote:
> On 11 June 2013 01:51, Andrew Schulman wrote:
> >> See here for additional information and reproducible steps in the mintty
> >> support ticket:
> >> https://code.google.com/p/mintty/issues/detail?id=390
> >>
> >> I can reproduce this using cygwin 1.7.20, 1.7.19
On 11 June 2013 01:51, Andrew Schulman wrote:
>> See here for additional information and reproducible steps in the mintty
>> support ticket:
>> https://code.google.com/p/mintty/issues/detail?id=390
>>
>> I can reproduce this using cygwin 1.7.20, 1.7.19, 1.7.18, 1.7.15, and 1.7.7.
>>
>> Screen does
On 6/13/2013 7:39 PM, g...@malth.us wrote:
On Thu, 13 Jun 2013, at 14:07, Larry Hall (Cygwin) thusly quipped:
On 6/13/2013 3:34 PM, Greg Turner wrote:
On Wed, Jun 12, 2013 at 3:19 PM, Matt D. wrote:
"the Windows console window you get through cygstart is not [a pty]"
Ah, so /that's/ what I
On Thu, 13 Jun 2013, at 14:07, Larry Hall (Cygwin) thusly quipped:
> On 6/13/2013 3:34 PM, Greg Turner wrote:
>> On Wed, Jun 12, 2013 at 3:19 PM, Matt D. wrote:
>>> "the Windows console window you get through cygstart is not [a pty]"
>>
>> Ah, so /that's/ what I recently read uncomprehendingly!
On 6/13/2013 3:34 PM, Greg Turner wrote:
On Wed, Jun 12, 2013 at 3:19 PM, Matt D. wrote:
"the Windows console window you get through cygstart is not [a pty]"
Ah, so /that's/ what I recently read uncomprehendingly! Thanks for
tracking down this concise explanation. Assuming that's right, the
On Wed, Jun 12, 2013 at 3:19 PM, Matt D. wrote:
> "the Windows console window you get through cygstart is not [a pty]"
Ah, so /that's/ what I recently read uncomprehendingly! Thanks for
tracking down this concise explanation. Assuming that's right, then,
I wonder: what is it?
-gmt
--
Problem
If you read the response from the mintty author in the support ticket
linked in the original post you'll see:
"There've been various issues with pseudo terminal (pty) layer in the
Cygwin 1.7.19 release, which apparently haven't been fully addressed in
1.7.20. Mintty is based on that pty layer,
> $ screen -S name -d -m
> $ screen -S name -x
> Remove dead screens with 'screen -wipe'.
> $
Sorry, typed by hand, corrected above.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscr
> See here for additional information and reproducible steps in the mintty
> support ticket:
> https://code.google.com/p/mintty/issues/detail?id=390
>
> I can reproduce this using cygwin 1.7.20, 1.7.19, 1.7.18, 1.7.15, and 1.7.7.
>
> Screen does NOT hang when is is created by calling the first c
13 matches
Mail list logo
