From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: V11db_gdbm.ztst fails on Cygwin
Date: Thu, 02 Mar 2017 11:54:07 +0000 [thread overview]
Message-ID: <20170302115407.29ee0dd9@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <1488455260.47056.897968424.73CCAA35@webmail.messagingengine.com>
On Thu, 02 Mar 2017 03:47:40 -0800
Sebastian Gniazdowski <psprint3@fastmail.com> wrote:
> Any idea how to write test result so that both hash key orders match?
The standard zsh test technique would be to put the output into an array
and sort that.
pws
next prev parent reply other threads:[~2017-03-02 12:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 10:52 Jun T.
2017-03-02 11:47 ` Sebastian Gniazdowski
2017-03-02 11:54 ` Peter Stephenson [this message]
2017-03-02 11:54 ` Daniel Shahaf
2017-03-02 12:14 ` Sebastian Gniazdowski
2017-03-02 15:16 ` Sebastian Gniazdowski
2017-03-02 23:56 ` Jun T.
2017-03-03 11:06 ` 淳一 滝本
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=20170302115407.29ee0dd9@pwslap01u.europe.root.pri \
--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).