Re: unbalanced parenthesis not recognized

2021-11-18 Thread Harald Dunkel
On 2021-11-18 17:52:29, Robert Elz wrote: Date:Thu, 18 Nov 2021 10:34:40 +0100 From:Harald Dunkel Message-ID: | at least due to unbalanced parenthesis? Greg's reply was correct, but he didn't explicitly address that point. In sh, characters like { } [ ] (but

Re: Unclosed quotes on heredoc mode

2021-11-18 Thread Chet Ramey
On 11/17/21 7:01 PM, Robert Elz wrote: > Date:Wed, 17 Nov 2021 15:47:37 -0500 > From:Chet Ramey > Message-ID: <420281e7-f3c4-8054-d390-9378080c2...@case.edu> > > | Every modern shell uses `$PATH' as the here-document delimiter > > Depends what you call modern shell

Re: unbalanced parenthesis not recognized

2021-11-18 Thread Robert Elz
Date:Thu, 18 Nov 2021 10:34:40 +0100 From:Harald Dunkel Message-ID: | at least due to unbalanced parenthesis? Greg's reply was correct, but he didn't explicitly address that point. In sh, characters like { } [ ] (but not ( and )) are just characters. In some scena

Re: unbalanced parenthesis not recognized

2021-11-18 Thread Greg Wooledge
On Thu, Nov 18, 2021 at 10:34:40AM +0100, Harald Dunkel wrote: > Hi folks, > > I am not sure, but shouldn't bash 5.1.4 complain about > > : ${SSLDIR}:="${JM_WORK}/ssl"} There's no syntax error here. It may be a bug, in the sense that it doesn't do what you wanted it to do, but from the sh

unbalanced parenthesis not recognized

2021-11-18 Thread Harald Dunkel
Hi folks, I am not sure, but shouldn't bash 5.1.4 complain about : ${SSLDIR}:="${JM_WORK}/ssl"} at least due to unbalanced parenthesis? The correct version would be : ${SSLDIR:="${JM_WORK}/ssl"} Regards Harri

Re: bash conditional expressions

2021-11-18 Thread Greg Wooledge
On Thu, Nov 18, 2021 at 07:26:51AM +0100, Michael J. Baars wrote: > So now we have a relation for 'older than' and for 'newer than', but how > about 'oldest' (executable), and 'newest' (executable)? https://mywiki.wooledge.org/BashFAQ/099 The bot in libera's #bash also has this factoid for it: