zsh-workers
 help / color / mirror / code / Atom feed
From: "Jun T." <takimoto-j@kba.biglobe.ne.jp>
To: zsh-workers@zsh.org
Subject: Re: Test failures on MacOS with latest pull from git
Date: Tue, 4 Nov 2014 23:59:41 +0900	[thread overview]
Message-ID: <66F59275-AF1C-40B7-82B2-535B538829A7@kba.biglobe.ne.jp> (raw)
In-Reply-To: <141103101835.ZM31940@torch.brasslantern.com>


2014/11/04 03:18, Bart Schaefer <schaefer@brasslantern.com> wrote:
> That's a good hypothesis, but a little strange because the zsh that
> starts up on the pty ought to be resetting that (just as one starting
> in a terminal window would).

Yes, the slave zsh should set up the slave tty properly when it starts.
But Zle would change the tty mode between canonical and non-canonical
modes back and forth. It seems the slave tty is still in the canonical
mode when it should not be (i.e., when reading the command line character
by character). But I don't know why this happens only with BSD-based pty.

Currently I have no time to go into any more detail, but I must say
I would not be able to get any real fix even if I have enough time.

The following is another possible workaround (X02zlevi.ztst need not be
patched if this patch is used).

Jun


diff --git a/Test/comptest b/Test/comptest
index 4655f3b..b6256cc 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
+stty 38400 columns 80 rows 24 werase undef
 TERM=vt100
 setopt zle
 autoload -U compinit


  reply	other threads:[~2014-11-04 15:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-30 23:27 Bart Schaefer
2014-10-31  0:53 ` Bart Schaefer
2014-10-31 12:56   ` Oliver Kiddle
2014-10-31 13:27     ` Vin Shelton
2014-10-31 14:06     ` Bart Schaefer
2014-10-31 18:08 ` Jun T.
2014-11-03 18:18   ` Bart Schaefer
2014-11-04 14:59     ` Jun T. [this message]
2014-11-08 20:16       ` Bart Schaefer
2014-11-08 22:11         ` Oliver Kiddle
2014-11-10 12:50           ` Jun T.

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=66F59275-AF1C-40B7-82B2-535B538829A7@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).