From: Thorsten Glaser <t.glaser@tarent.de>
To: Jilles Tjoelker <jilles@stack.nl>
Cc: Oleg Bulatov <oleg@bulatov.me>,
dash@vger.kernel.org, miros-mksh@mirbsd.org
Subject: Re: heredoc and subshell
Date: Wed, 24 Feb 2016 09:46:24 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1602240942580.2671@tglase-nb.lan.tarent.de> (raw)
In-Reply-To: <20160223231843.GA55161@stack.nl>
(Thanks to izabera for bringing this to my attention!)
On Wed, 24 Feb 2016, Jilles Tjoelker wrote:
> On Wed, Feb 24, 2016 at 01:07:44AM +0300, Oleg Bulatov wrote:
> > --- bash 4.3.42 output:
That’s the output I’d expect, from manually reading this.
> Interestingly, mksh parses this in yet another way. In unmodified form,
> it fails with here document 'XXX' unclosed.
Yeah, I noticed… yay another bug to fix (just had two last night)…
> After appending an XXX line, it outputs:
Ah okay, thanks for this hint, that should make debugging easier.
bye,
//mirabilos
--
Sometimes they [people] care too much: pretty printers [and syntax highligh-
ting, d.A.] mechanically produce pretty output that accentuates irrelevant
detail in the program, which is as sensible as putting all the prepositions
in English text in bold font. -- Rob Pike in "Notes on Programming in C"
prev parent reply other threads:[~2016-02-24 8:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 22:07 heredoc and subshell Oleg Bulatov
2016-02-23 22:49 ` Eric Blake
2016-02-23 23:16 ` Eric Blake
[not found] ` <56CCE1E3.1060805-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-02-24 10:58 ` Joerg Schilling
[not found] ` <56cd8cd1.LdVYbpfe+0tQMm8I%Joerg.Schilling-8LS2qeF34IpklNlQbfROjRvVK+yQ3ZXh@public.gmane.org>
2016-02-24 12:27 ` Shware Systems
2016-02-24 12:32 ` Joerg Schilling
2016-02-24 20:27 ` Oleg Bulatov
2016-02-23 23:18 ` Jilles Tjoelker
2016-02-24 8:46 ` Thorsten Glaser [this message]
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=alpine.DEB.2.20.1602240942580.2671@tglase-nb.lan.tarent.de \
--to=t.glaser@tarent.de \
--cc=dash@vger.kernel.org \
--cc=jilles@stack.nl \
--cc=miros-mksh@mirbsd.org \
--cc=oleg@bulatov.me \
/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 NNTP newsgroup(s).