From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Confirming X02zlevi test failures
Date: Thu, 20 Nov 2014 09:18:03 -0800 [thread overview]
Message-ID: <141120091803.ZM3693@torch.brasslantern.com> (raw)
In-Reply-To: <5A1A98B7-42E0-4EE1-9468-32E2D6434246@kba.biglobe.ne.jp>
On Nov 21, 12:42am, Jun T. wrote:
}
} Next I replaced TCSADRAIN by TCSANOW in settyinfo() (utils.c, line 1554),
} and now 'swap case on a blank line' in X02zlevi.ztst seems to succeed.
} But I don't know what kind of unwanted side effects it may cause.
It'll cause typeahead to be misinterpreted when using a "real" terminal
device, I fear. It took a lot of work back in the day to get that tty
draining stuff right.
} Moreover, if 'werase undef' is removed from comptest, line 37, then
} X02zlevi.ztst fails again at
} 'line based put before followed by character based yank-pop'.
I begin to suspect that what needs to happen is that zpty needs to be a
lot more aggressive internally about consuming (and buffering up) the
slave output as fast as it appears, even if a zpty read call has not
yet been made from the shell. Clearly the slave can "see" it's own
output if the master doesn't manage to grab it first.
next prev parent reply other threads:[~2014-11-20 17:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 16:50 Bart Schaefer
2014-11-19 17:25 ` Ray Andrews
2014-11-19 23:05 ` Oliver Kiddle
2014-11-20 6:20 ` Bart Schaefer
2014-11-20 15:42 ` Jun T.
2014-11-20 17:18 ` Bart Schaefer [this message]
2014-11-21 14:37 ` Oliver Kiddle
2014-11-21 18:18 ` Jun T.
2014-11-21 18:56 ` Bart Schaefer
2014-11-23 1:37 ` Jun T.
2014-11-23 3:32 ` Bart Schaefer
2014-11-23 7:44 ` Jun T.
2014-11-24 0:11 ` Bart Schaefer
2014-11-23 9:00 ` Oliver Kiddle
2014-11-23 18:37 ` Bart Schaefer
2014-11-25 17:13 ` Jun T.
2014-11-25 17:32 ` Jun T.
2014-11-25 19:01 ` Bart Schaefer
2014-11-26 2:31 ` Jun T.
2014-11-26 14:51 ` Oliver Kiddle
2014-11-26 15:45 ` Peter Stephenson
2014-11-26 16:37 ` Bart Schaefer
2014-11-27 14:11 ` Oliver Kiddle
2014-12-01 10:58 ` Jun T.
2014-12-05 14:36 ` Oliver Kiddle
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=141120091803.ZM3693@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).