On Sat, 14 Dec 2019 09:03:26 +, cho...@jtan.com wrote:
> This is certainly not the best way to do this but it does the job:
>
> In particular it just reeks of kludge, which I'm not happy with
> because according to the comment two-dozen lines up it's already a
> kludge. The loop is lifted
Hi Matthew,
I'm unable to judge the patch, but appreciate your quick fix. Thanks a
lot! I'm looking forward to the next release, in which it is contained.
I just occurred to me, that the problem also exists for ". Is this
covered with your patch as well?
Richard
cho...@jtan.com wrote:
> Richard
On Sat, Dec 14, 2019 at 09:03:26AM +, cho...@jtan.com wrote:
> Richard Ulmer writes:
> > Hi,
> > when there is a single ' in a comment within a subshell, I get this
> > error: foo[6]: no closing quote
> >
> > Here is an example script to reproduce the problem:
> >
> > foo=$(
> > # It's
Richard Ulmer writes:
> Hi,
> when there is a single ' in a comment within a subshell, I get this
> error: foo[6]: no closing quote
>
> Here is an example script to reproduce the problem:
>
> foo=$(
> # It's bar:
> echo bar
> )
> echo $foo
This is certainly not the best way to do this
Hi,
when there is a single ' in a comment within a subshell, I get this
error: foo[6]: no closing quote
Here is an example script to reproduce the problem:
foo=$(
# It's bar:
echo bar
)
echo $foo
I found this behaviour unexpected und suspect it's a bug. I had
encountered this as
5 matches
Mail list logo
