From: Bart Schaefer <schaefer@brasslantern.com>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: "Zsh hackers' list" <zsh-workers@zsh.org>
Subject: Re: PATCH: fg and bg tests
Date: Wed, 25 Apr 2018 10:55:55 -0700 [thread overview]
Message-ID: <CAH+w=7Y_xL+UbwrFt_L1TCq+b2jEr53tb5XmOrG+uUiE4af9rA@mail.gmail.com> (raw)
In-Reply-To: <20180425184110.3de75e94@camnpupstephen.cam.scsc.local>
On Wed, Apr 25, 2018 at 10:41 AM, Peter Stephenson
<p.stephenson@samsung.com> wrote:
>
> With a bit of luck, dc is easier to manage all round.
Sadly:
./W02jobs.ztst: starting.
Pattern match filead, line mismatch (6/9):
<1
<zsh:*(stopped|suspended)*dc*
<*continued*dc*
<*(stopped|suspended)*dc*
<*continued*dc*
<2
>1
>zsh: suspended dc 2> /dev/null
>[1] + continued dc 2> /dev/null
>[1] + suspended (tty input) dc 2> /dev/null
>[1] + continued dc 2> /dev/null
>zsh: command not found: 1
>zsh: command not found: +
>zsh: command not found: p
>zsh: command not found: q
Test ./W02jobs.ztst failed: output differs from expected as shown above for:
zpty_start
zpty_input $'dc 2>/dev/null\n1\np\n'
zpty_line
zpty_input $'\C-z'
zpty_input 'bg'
zpty_input 'fg'
zpty_input $'1\n+\np\nq\n'
zpty_stop
Was testing: bg and fg with user input
next prev parent reply other threads:[~2018-04-25 17:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180424125946eucas1p1f04c37866bb05e4a72edf4259af38238@eucas1p1.samsung.com>
2018-04-24 12:59 ` Peter Stephenson
[not found] ` <CGME20180425090941eucas1p187cf5d07341d2041c15e9947962f3bd9@eucas1p1.samsung.com>
2018-04-25 9:09 ` Peter Stephenson
2018-04-25 10:32 ` Stephane Chazelas
2018-04-25 14:28 ` Bart Schaefer
2018-04-25 14:56 ` Peter Stephenson
2018-04-25 17:01 ` Peter Stephenson
2018-04-25 17:16 ` Bart Schaefer
2018-04-25 17:41 ` Peter Stephenson
2018-04-25 17:55 ` Bart Schaefer [this message]
2018-04-26 8:08 ` Peter Stephenson
2018-04-26 14:37 ` Bart Schaefer
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='CAH+w=7Y_xL+UbwrFt_L1TCq+b2jEr53tb5XmOrG+uUiE4af9rA@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=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).