zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: <zsh-workers@zsh.org>
Subject: Re: W02jobs.ztst hangs with zsh 5.6.1
Date: Mon, 10 Sep 2018 16:14:26 +0100	[thread overview]
Message-ID: <20180910151428eucas1p17e62bab7b6d218d45d0b82f21af8df1f~TErVhouMz0413304133eucas1p1x@eucas1p1.samsung.com> (raw)
In-Reply-To: <524677991.1156882.1536578389106@mail2.virginmedia.com>

On Mon, 10 Sep 2018 12:19:49 +0100 (BST)
Peter Stephenson <p.w.stephenson@ntlworld.com> wrote:
> I'd be very surprised if it failed, as all the hairiness here is in
> the use of zpty in the test system, which I've had a lot of trouble
> with when trying to add new tests.

It's unlikely zpty is going to get enough love and attention to be
robust enough for what we really need here.

I wonder if there is some replacement we could use that someone might
already know about?  The Python pty module looked like it might be
usable, but I encountered half a dozen Python-style illogicalities before
getting a dozen lines into a programme, so we'll need some existing
script to start with.

pws

  parent reply	other threads:[~2018-09-10 15:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20180910102119epcas5p384cea9ba5749eb81be99c4f4d85a954e@epcas5p3.samsung.com>
2018-09-10 10:20 ` İsmail Dönmez
2018-09-10 10:32   ` Peter Stephenson
2018-09-10 10:39     ` İsmail Dönmez
2018-09-10 11:19       ` Peter Stephenson
2018-09-10 11:32         ` İsmail Dönmez
2018-09-10 12:46           ` Peter Stephenson
2018-09-10 13:07             ` İsmail Dönmez
2018-09-10 15:14         ` Peter Stephenson [this message]
2018-09-10 15:50           ` Daniel Shahaf
2018-09-10 16:22             ` Peter Stephenson
2018-09-10 16:55               ` Bart Schaefer
2018-09-10 17:40                 ` Peter Stephenson

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='20180910151428eucas1p17e62bab7b6d218d45d0b82f21af8df1f~TErVhouMz0413304133eucas1p1x@eucas1p1.samsung.com' \
    --to=p.stephenson@samsung.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).