DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:references:to:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=FJm/khnfA+fashLO
	jaPZyvcypUftNqoHBPJCiWj7edd+LpgqdNZNSu3X1KFyuCE+ZngwOwOUJC+L6pSQ
	Kf7TFnQQFuusOLD0OrDtQT5MEf8FfMYoGh6kKdF51tCZ6BvuX5SByYysQL6Hb0c9
	EPv8fTcDkcdTTYO4id2G0/hEucE=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Reply-to: cygwin AT cygwin DOT com
Subject: Re: Some programs (vi, ssh) crash when screen buffer height is big
References: <CAHV8iDH4pG0FoGrckc36atQUV+SWOnryJ-zBDK92HTGgPRC=Ew AT mail DOT gmail DOT com> <26A19798-1F20-4D52-A311-C8312E0D4621 AT etr-usa DOT com> <CAHV8iDGU8tN+58LR10e3zHxiEsr5ekXrKrLeyYRAD0tx0H6B1A AT mail DOT gmail DOT com> <6DC9320F-4DCC-47E4-AB8C-3158EBD6260E AT etr-usa DOT com> <CAHV8iDFauqCe-aKZB6Ba1oJbOvvOr7M19ZyJJVu-t8DQ46f=ug AT mail DOT gmail DOT com> <CAN=he+XN0qiLjm+K+0Qr13=GqtvAyJSArdFh873++1=dTjP35Q AT mail DOT gmail DOT com> <CAHV8iDH=FL3XQ0OrK0pzLPOP+7-VK88HvD2_k2zzWZTc+hyXdw AT mail DOT gmail DOT com> <55DC9C55 DOT 9090404 AT gmail DOT com> <CAHV8iDEw1fp4-yXLd1sjKMvKvCzemuEFNbUy4FJ-zvxWQZC26g AT mail DOT gmail DOT com> <55DFB10C DOT 3050804 AT cygwin DOT com> <CAHV8iDGw3FWOBBdNQ0HcBCpwAHRQrpTj6YbNjE8o4AnCe77zqA AT mail DOT gmail DOT com>
To: cygwin AT cygwin DOT com
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Message-id: <55E0AA2E.1030403@cygwin.com>
Date: Fri, 28 Aug 2015 14:36:30 -0400
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-version: 1.0
In-reply-to: <CAHV8iDGw3FWOBBdNQ0HcBCpwAHRQrpTj6YbNjE8o4AnCe77zqA@mail.gmail.com>
Content-type: text/plain; charset=windows-1252; format=flowed
Content-transfer-encoding: 7bit

On 08/28/2015 09:23 AM, Sous Lesquels wrote:
> Thanks Larry.
>
>> I think you're misunderstanding where the limitation is coming from.
>
> I don't think I'm misunderstanding anything - I was actually thinking
> along the same lines that you just wrote.

OK, good. We're on the same page then.  :-)

> I feel that with increasing monitors sizes == increasing window sizes,
> it might happen more often, as not all people use mintty. I can change
> from ConEmu to mintty, but IMHO that's like saying I can use the
> stairs instead of an elevator in Burj Khalifa. I don't and cannot
> expect anything from Cygwin team, which is providing something I like
> and use every day. If there are more important problems that mine
> never comes to the top, then that's what it is.

Well, if there is a change in ConEmu and/or MS support here, then it
all comes for free. ;-)  As I said, I'm not saying that there's
absolutely nothing that could be done to address this in Cygwin but I'm
also not saying that there is.  It is clearly a limitation that currently
has no known work-around for the specific issue without avoiding the MS
console.

> I still hope someone will be able to check. It looks to me this might
> be one of those "640k will be enough" problems, with some buffer with
> fixed size that nobody anticipated will not be "big enough". Or it
> might be something completely different. Even if it's just me that's
> affected, I understandably would like that to stop happening. If it
> does, I'd be so much happier. If it doesn't, tough luck. I've been
> dealing with several dozen restarts each day for at least a year when
> I first reported the problem, but I still like it and use it.

Yeah, I understand the frustration and it's certainly not wrong of
you to report the problem you're seeing.  And be assured that your
report isn't ignored.  But it is something that may be difficult to
address in Cygwin's console support so  it's hard to say there's going
to be a good solution coming from Cygwin itself soon, unless there's
some developer that wants to chase this in the near-term.

> Saying "it's ms bug", "it's a design choice", "it's a bug, but we
> don't have time / resources to fix it", "it happens so rarely, we
> don't care", "it's going to be fixed in 2030", etc. is fine with me.
> It might mean that I should not expect this to work any time soon or
> ever, but it would be a honest answer and, if coming from someone on
> the team itself, hopefully correct. Instead, a few different people
> replied to me on this thread with "you misunderstanding, ignorant
> quack".

I'm pretty sure that no-one actually meant to imply that you're an
"ignorant quack".  I can also say that Cygwin does support the MS
console to the extent that the MS console API allows.  That's not to
say there aren't bugs in that support or that any bugs aren't considered.
It seems you've found such a bug so I will thank you for reporting it.
And while I can't speak for any of the developers on this list, I only
wanted to impart that this issue is likely to be viewed as relatively
low priority, given the specifics of the issue and the alternatives.
You shouldn't interpret my response as one that indicates that the bug
won't be addressed or that your report isn't appreciated.  My only goal
was to try to give you the feedback you were looking for.  With some
luck, someone will find the solution to this problem even if they aren't
really looking for it and, you never know, that could happen real soon!
So I hope you find this feedback to be helpful in answering some of your
inquiries.

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

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