From: "Jun T." <takimoto-j@kba.biglobe.ne.jp>
To: zsh-workers@zsh.org
Subject: Re: Confirming X02zlevi test failures
Date: Sun, 23 Nov 2014 16:44:59 +0900 [thread overview]
Message-ID: <21240C97-F8F1-45F7-8F15-4454D4066276@kba.biglobe.ne.jp> (raw)
In-Reply-To: <141122193250.ZM15938@torch.brasslantern.com>
2014/11/23 12:3, Bart Schaefer <schaefer@brasslantern.com> wrote:
> OK, so maybe what we needed all along instead of those zpty_flush calls
> was to have a timeout delay.
Sorry, my post was not clear enough.
I need BOTH zpty_flush and '-t 0.02' to get 1000/1000 success.
With zpty_flush only, I got 998/1000 success on Mac (1000/1000 on FreeBSD).
So this is a kind of yet another workaround.
But the result supports your guess that clearing the buffer of the slave
tty would be important.
diff --git a/Test/comptest b/Test/comptest
index c67237a..5964114 100644
--- a/Test/comptest
+++ b/Test/comptest
@@ -34,7 +34,7 @@ comptestinit () {
"fpath=( $fpath )" \
"bindkey -$comptest_keymap" \
'LISTMAX=10000000
-stty 38400 columns 80 rows 24 werase undef tabs
+stty 38400 columns 80 rows 24 tabs -icanon -iexten
TERM=vt100
KEYTIMEOUT=1
setopt zle
@@ -162,9 +162,9 @@ comptest () {
zletest () {
local first=0
for input; do
+ zpty_flush Before zletest
# sleep for $KEYTIMEOUT
- (( first++ )) && read -t 0.011 -k 1 < /dev/null
- # zpty_flush Before zletest
+ (( first++ )) && read -t 0.02 -k 1 < /dev/null
zpty -n -w zsh "$input"
done
zpty -n -w zsh $'\C-X'
@@ -172,6 +172,6 @@ zletest () {
print "failed to invoke finish widget."
return 1
}
- # zpty_flush After zletest
+ zpty_flush After zletest
print -lr "${(@)${(@ps:\r\n:)log##*<WIDGET><finish>}[2,-2]}"
}
next prev parent reply other threads:[~2014-11-23 8:24 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
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. [this message]
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=21240C97-F8F1-45F7-8F15-4454D4066276@kba.biglobe.ne.jp \
--to=takimoto-j@kba.biglobe.ne.jp \
--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).