public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Some programs (vi, ssh) crash when screen buffer height is big
Date: Fri, 28 Aug 2015 13:23:00 -0000	[thread overview]
Message-ID: <55DFB10C.3050804@cygwin.com> (raw)
In-Reply-To: <CAHV8iDEw1fp4-yXLd1sjKMvKvCzemuEFNbUy4FJ-zvxWQZC26g@mail.gmail.com>

On 08/27/2015 11:39 AM, Sous Lesquels wrote:
> Thanks cyg Simple.
>
>> It depends on the level of support you want from this list
>
> In this case, if Cygwin is supposed to work with the regular windows
> console? If mintty was created due to Cygwin *not working as expected*
> on default windows console, that's a good answer, as long as it's
> correct. If Cygwin *should* work on default windows console, then I
> would appreciate someone explaining if there's a workaround, if this
> would be considered a candidate for development any time soon, things
> like that.
>
> I don't expect anything. I'm not paying others to develop. I do hope
> the bugs are fixed, one way or another, as I use Cywgin daily, so of
> course I'd like it to work in an environment I have and like.

I think you're misunderstanding where the limitation is coming from.
The console itself is limited in functionality compared to what's
expected of a terminal.  Cygwin can only do so much to smooth out
those limitations.  This particular issue is a corner case, perhaps
an extreme corner case.  If there is some work-around that could be
found and/or implemented, it's probably of limited value in general
so it's likely that someone with the itch will need to chase
this down and implement a workaround if possible.  Besides that, the
alternatives are to side-step the console limitations by using mintty
or take this upstream to ComEmu or MS.


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

  reply	other threads:[~2015-08-28  0:53 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) [this message]
2015-08-28 14:05                   ` Sous Lesquels
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=55DFB10C.3050804@cygwin.com \
    --to=reply-to-list-only-lh@cygwin.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).