From: Bart Schaefer <schaefer@brasslantern.com>
To: "Jun T." <takimoto-j@kba.biglobe.ne.jp>, zsh-workers@zsh.org
Subject: Re: padding in vt100 causes 'make check' to hang on FreeBSD
Date: Mon, 16 Dec 2013 08:33:08 -0800 [thread overview]
Message-ID: <131216083308.ZM1861@torch.brasslantern.com> (raw)
In-Reply-To: <30173FEA-DCF9-480B-A219-232505B4311F@kba.biglobe.ne.jp>
On Dec 17, 12:36am, Jun T. wrote:
}
} Various capabilities of vt100 contain the ancient "padding", and FreeBSD's
} slave side tputs() actually sends 'null bytes' as paddings before sending
} the <PROMPT>. But the zsh on the master side just considers the 'null byte'
} as the end of C-string, and the line 96 never returns.
I would be willing to bet this is happening because of this (README):
The variable BAUD is no longer set automatically by the shell.
In previous versions it was set to the baud rate reported by
the terminal driver in order to initialise the line editor's
compensation mechanism for slow baud rates. However, the baud
rate so reported is very rarely related to the limiting speed of
screen updates on modern systems. Users who need the compensation
mechanism should set BAUD to an appropriate rate by hand.
Please try the following and let us know if it helps:
diff --git a/Test/comptest b/Test/comptest
index 5577209..645a963 100644
--- a/Test/comptest
+++ b/Test/comptest
@@ -35,6 +35,7 @@ comptestinit () {
"bindkey -$comptest_keymap" \
'LISTMAX=10000000
TERM=vt100
+BAUD=38400
stty columns 80 rows 24
setopt zle
autoload -U compinit
next prev parent reply other threads:[~2013-12-16 16:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 15:36 Jun T.
2013-12-16 16:33 ` Bart Schaefer [this message]
2013-12-16 17:13 ` Jun T.
2013-12-16 18:21 ` Bart Schaefer
2013-12-17 5:29 ` J. Takimoto
2013-12-17 6:06 ` Bart Schaefer
2013-12-16 18:29 ` Axel Beckert
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=131216083308.ZM1861@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=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).