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, 18 Jul 2014 15:51:00 -0000	[thread overview]
Message-ID: <53C9427A.4030104@cygwin.com> (raw)
In-Reply-To: <CAHV8iDHFYe__rQ5ghDNgHfj_GJ6ObVDfmx4u9aXRDzURN-C8UQ@mail.gmail.com>

On 07/18/2014 10:48 AM, sous lesquels wrote:
>> It's not reproducible for me.  I just tried your ssh scenario with a
>> 1000 and 2000 line buffers and it works fine for me every time, be it
>> with Cygwin 1.7.30 or the latest snapshot.  I also raised the number of
>> loops.  Is it possible that you're suffering a BLODA(*) problem?
>>
>>
>> Thanks,
>> Corinna
>
>> Confirmed.
>>
>> I tried up to 9999, the maximum allowed.
>>
>> This is under Windows 8.1 Pro, with Cygwin 1.7.30, both 32- and 64-bit.
>
> I was running under:
>
> CYGWIN_NT-6.1 1.7.29(0.272/5/3) 2014-04-07 13:46
>
> It might have been a feature present in 1.7.29.
>
> More likely, it was a installation issue. I had cygwin1.dll with
> 1.7.29 and cygwin1.dll.new with 1.7.30. I ran setup-x86_64.exe
> multiple times and it did nothing to upgrade it (I assume it renames
> cygwin1.dll.new to cygwin1.dll, correct?). No cywgin processes were
> running otherwise. What helped is to manually reinstall "cygwin"
> package. Now that I'm at 1.7.30, all seems OK. Probably just a version
> mismatch.

This is not the recommended way of handling this situation.  You end up
with a ".new" extension if the DLL was in use at the time of your upgrade.
In this case, setup*.exe schedules a replace of your existing DLL with the
".new" version on reboot.  So if you find such a file on your system, the
sanctioned resolution to this is to reboot.

> As a side topic, I did not get a mail with your (Corinna / Warren)
> replies, just a digest, and could not reply to it. Not sure how it
> will thread. Is there a way to somehow specify which post to reply to
> in the body of the mail, so that it threads as I want? As per
> https://sourceware.org/lists.html#what-software, ezmlm-idx is used and
> as per http://untroubled.org/ezmlm/faq/How-threading-works.html#How-threading-works
> it threads by subject, not using In-Reply-To or so. And even if it
> did, I cannot specify headers via Gmail (firewall, cannot use other
> email clients unfortunately). If not a simple answer, I'll open a
> separate thread.

You must have subscribed to the list and requested a digest.  By
default, any email replies to this list go to the list.  If you
want a direct copy, you have to ask for it and you rely on the
kindness of the responder to put in the extra effort to comply.
The best way to get individual messages from this list that are easy
to reply to is to subscribe without using the digest option.


-- 
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:[~2014-07-18 15:51 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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) [this message]
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
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
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

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=53C9427A.4030104@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).