public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Sous Lesquels <a9f54d2@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Some programs (vi, ssh) crash when screen buffer height is big
Date: Fri, 28 Aug 2015 14:05:00 -0000	[thread overview]
Message-ID: <CAHV8iDGw3FWOBBdNQ0HcBCpwAHRQrpTj6YbNjE8o4AnCe77zqA@mail.gmail.com> (raw)
In-Reply-To: <55DFB10C.3050804@cygwin.com>

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.

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.

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.

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

--
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:[~2015-08-28 13:23 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20 16:35 Sous Lesquels
2015-08-20 21:45 ` Warren Young
2015-08-20 22:21   ` Sous Lesquels
2015-08-20 22:36     ` Warren Young
2015-08-21 12:37       ` Sous Lesquels
2015-08-21 18:53         ` Warren Young
2015-08-21 21:41         ` Thomas Wolff
2015-08-24 12:08         ` Philip Daniels
2015-08-25 16:35           ` Sous Lesquels
2015-08-25 16:47             ` cyg Simple
2015-08-27 19:47               ` Sous Lesquels
2015-08-28 13:23                 ` Larry Hall (Cygwin)
2015-08-28 14:05                   ` Sous Lesquels [this message]
2015-08-28 18:50                     ` Larry Hall (Cygwin)
2015-08-28 21:31                       ` Sous Lesquels
2015-08-28 21:53                         ` Warren Young
2015-08-28 23:24                     ` Warren Young
2015-08-25 18:20             ` Andrey Repin
2015-08-27 20:00               ` Sous Lesquels
2015-08-28 14:48                 ` Andrey Repin
2015-08-28 21:09                   ` Sous Lesquels
2015-08-28 23:27                     ` Andrey Repin
2015-08-20 22:35   ` Andrey Repin
  -- strict thread matches above, loose matches on Subject: below --
2014-07-16 20:10 sous lesquels
2014-07-16 20:30 ` sous lesquels
2014-07-17  2:13   ` Christopher Faylor
2014-07-17  8:24   ` Corinna Vinschen
2014-07-18  3:28     ` Warren Young
2014-07-18 14:48   ` sous lesquels
2014-07-18 15:51     ` Larry Hall (Cygwin)
2014-07-18 16:59       ` sous lesquels
2014-07-18 17:59         ` Christopher Faylor
2014-07-18 18:48           ` Nellis, Kenneth
2014-07-18 20:35             ` sous lesquels
2014-07-21 12:32               ` Nellis, Kenneth
2014-07-23  0:50                 ` Christopher Faylor

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=CAHV8iDGw3FWOBBdNQ0HcBCpwAHRQrpTj6YbNjE8o4AnCe77zqA@mail.gmail.com \
    --to=a9f54d2@gmail.com \
    --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).