From: "Jürgen Wagner" <juergen@wagner.is>
To: cygwin@cygwin.com
Subject: Re: Challenge: a VERY strange problem with command substitution in bash
Date: Tue, 11 Jul 2017 19:16:00 -0000 [thread overview]
Message-ID: <ab083551-a47d-35b3-0986-f237c335f426@wagner.is> (raw)
In-Reply-To: <93b0a4e1-78eb-798e-9946-cd38ab288cce@wagner.is>
[-- Attachment #1: Type: text/plain, Size: 105 bytes --]
Sorry, little omission: the first example under section 3 is not with
bash, it was done with dash.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3986 bytes --]
next prev parent reply other threads:[~2017-07-11 19:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 19:12 Jürgen Wagner
2017-07-11 19:16 ` Jürgen Wagner [this message]
2017-07-11 20:40 ` Jürgen Wagner
2017-07-11 23:22 ` Steven Penny
2017-07-11 23:24 ` Richard Beels via cygwin
[not found] ` <59655e58.d532240a.ae3d8.4253SMTPIN_ADDED_MISSING@mx.google.com>
2017-07-12 6:08 ` Wouter van Doorn
[not found] ` <20170711232506.02CE91C3666@atlantis.udag.de>
2017-07-28 18:03 ` Jürgen Wagner
2017-12-04 13:01 Erik Haukjær Andersen
2017-12-04 13:22 ` David Macek
2017-12-04 21:41 ` Brian Inglis
2017-12-04 20:20 ` Andrey Repin
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=ab083551-a47d-35b3-0986-f237c335f426@wagner.is \
--to=juergen@wagner.is \
--cc=cygwin@cygwin.com \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).