public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Doug Henderson <djndnbvg@gmail.com>
To: cygwin <cygwin@cygwin.com>
Subject: Re: [ANNOUNCEMENT] Updated: mintty 2.7.4
Date: Tue, 07 Feb 2017 01:03:00 -0000	[thread overview]
Message-ID: <CAJ1FpuPTRUKBn99ye7WyaAK-Ajf=burdJL3zdHtSZaiP_gXRBA@mail.gmail.com> (raw)
In-Reply-To: <52fb66c3-5dc5-afd7-02bf-acdb0a2a9972@towo.net>

On 6 February 2017 at 12:46, Thomas Wolff wrote:
> Am 05.02.2017 um 21:36 schrieb Brian Inglis:
>>
>> On 2017-02-05 11:35, Thomas Wolff wrote:
>>>
>>> Hi Achim,
>>>
>>> Am 04.02.2017 um 17:13 schrieb Achim Gratz:
>>>>
>>>> Thomas Wolff writes:
>>>>>
>>>>> I have uploaded mintty 2.7.4 with the following changes:

This may be a whisper from the distant past when some glass ttys moved
the cursor to the next line when you wrote to the last column of a
line, and others did not move the cursor until you wrote the next
character. Or they were different depend the width mode: 80 or 132
characters.

A virtual terminal handler, such as curses, had to know which behavior
would occur on the physical terminal in order to correctly maintain
the virtual terminal cursor position. When you did not know what the
physical terminal would do, you had to avoid writing to the 80th
column, or use safe cursor positioning that would work in either case.

Back in the day, I wrote a full screen editor that was usable with a
luggable glass tty with a 300 baud acoustic modem. Optimizing the data
stream was an extreme priority.

I also enhanced the terminal emulator that came with Plan 9 to more
fully emulate DEC's VT100 family of physical terminals when connected
to various remote mini's and mainframes running full screen apps.

When you don't know the precise behavior of a terminal or terminal
emulator, you must fallback to "safe" defaults. You can't always trust
the TERM variable. If you're lucky, you will get a standard
answer-back, which, in the case of a terminal emulator, may be
faithfully emulated.

Programs like screen and tmux throw themselves into the middle of this muddle.

HTH or at least entertained
Doug

-- 
Doug Henderson, Calgary, Alberta, Canada - from gmail.com

--
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:[~2017-02-07  1:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-27 21:45 Thomas Wolff
2017-02-04 16:13 ` Achim Gratz
2017-02-05 18:36   ` Thomas Wolff
2017-02-05 18:55     ` Achim Gratz
2017-02-06 19:16       ` Achim Gratz
2017-02-06 19:29         ` Thomas Wolff
2017-02-05 20:36     ` Brian Inglis
2017-02-06 19:46       ` Thomas Wolff
2017-02-07  1:03         ` Doug Henderson [this message]
2017-02-07  7:31         ` Brian Inglis
2017-02-07 20:52           ` Thomas Wolff
2017-02-08  2:17             ` Brian Inglis
2017-02-08 18:35             ` Achim Gratz
2017-02-08 22:52               ` Thomas Wolff
2017-02-09 19:37                 ` Thomas Wolff
2017-02-09 19:42                   ` Achim Gratz
2017-02-09 20:09                     ` Thomas Wolff
2017-02-07 21:00           ` diagnostic character info (Re: [ANNOUNCEMENT] Updated: mintty 2.7.4) Thomas Wolff
2017-02-09 19:38             ` Thomas Wolff

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='CAJ1FpuPTRUKBn99ye7WyaAK-Ajf=burdJL3zdHtSZaiP_gXRBA@mail.gmail.com' \
    --to=djndnbvg@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).