From: Peter Stephenson <p.stephenson@samsung.com>
To: Zsh hackers' list <zsh-workers@zsh.org>
Subject: Re: PATCH: fg and bg tests
Date: Wed, 25 Apr 2018 18:41:10 +0100 [thread overview]
Message-ID: <20180425184110.3de75e94@camnpupstephen.cam.scsc.local> (raw)
In-Reply-To: <CAH+w=7ZoMcrLvctSnUv7RuA=W555J1HenpbOD55X7ZFr3XPQ7Q@mail.gmail.com>
On Wed, 25 Apr 2018 10:16:34 -0700
Bart Schaefer <schaefer@brasslantern.com> wrote:
> (Regular work hours for me here now so promptness and length of reply
> are limited.)
>
> On Wed, Apr 25, 2018 at 10:01 AM, Peter Stephenson
> <p.stephenson@samsung.com> wrote:
> >
> > dc is even less verbose [...] So let's try that.
>
> For what it's worth, "ed" on MacOS seems to be prompting with a "?"
> after every command. Your first though about ignoring everything
> until the final result would probably have worked.
Hmm... the non-MacOS ed documentation seem fairly clear that prompting
is off by default and when it's on it's a "*" (unless there's an error).
Anyway, ignoring output turned out to be harder than expected ---
finding a consistent point in the code that didn't give blank
lines (that I couldn't necessarily rely on being present) wasn't that
easy. I'd probably have needed to edit the output to compare only
relevant lines.
With a bit of luck, dc is easier to manage all round.
pws
next prev parent reply other threads:[~2018-04-25 17:41 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 [this message]
2018-04-25 17:55 ` Bart Schaefer
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=20180425184110.3de75e94@camnpupstephen.cam.scsc.local \
--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).