public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@yandex.ru>
To: Thomas Wolff <towo@towo.net>, cygwin@cygwin.com
Subject: Re: Cygwin terminal weirdness
Date: Tue, 15 Sep 2015 09:50:00 -0000	[thread overview]
Message-ID: <1277809625.20150915124816@yandex.ru> (raw)
In-Reply-To: <55F7D781.3050606@towo.net>

Greetings, Thomas Wolff!

>>>> Call "man" on a sufficiently long topic. man bash would be quite sufficient.
>>>> Or just `less` a long enough text.
>>>> Hold down "End" key.
>>>> The screen buffer will jump and tear repeatedly, until you release the key.
>> ... as I can't reproduce it with PuTTY in the same situation.
> With putty, try the Home key instead. If you hold that, the result will 
> look even worse. Or try to hold the Down key at the end (of man bash) – 
> not good either.

Okay, it seems to really depends on the length of the scrollback buffer under
the hood.
Wasn't able to reproduce it with Home as you suggested, but observed it with
(again) End, when I tried to `less /var/log/syslog`. Which is, quite
unsurprisingly, quite long.
Though, the effect is minimal, it is still present.
Which confirms that it is, seemingly, less's, and not Cygwin's, fault.

> Slightly different effects in different environments are simply the 
> result of timing. You cannot completely avoid such effects if the window 
> contents is rewritten repeatedly.

The timing differences can be attributed to environment. I've been comparing
some string function implementations recently, and Windows seems to be real,
real slow. Like, 10 times slower than Linux, which I can't really explain with
hardware difference. (Win/i5 vs. Linux/G1620)


-- 
With best regards,
Andrey Repin
Tuesday, September 15, 2015 12:42:23

Sorry for my terrible english...

      reply	other threads:[~2015-09-15  9:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-13 18:50 Andrey Repin
2015-09-14 19:46 ` cyg Simple
2015-09-15  4:05   ` Andrey Repin
2015-09-14 20:09 ` Warren Young
2015-09-15  4:05   ` Andrey Repin
2015-09-15  8:32     ` Thomas Wolff
2015-09-15  9:50       ` Andrey Repin [this message]

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=1277809625.20150915124816@yandex.ru \
    --to=anrdaemon@yandex.ru \
    --cc=cygwin@cygwin.com \
    --cc=towo@towo.net \
    /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).