Re: "Variation" in Command Substitution Behaviour

2017-02-28 Thread Geoff Hull
Hi Reuti, Andreas, Yes, forgot to mention the bash versions I have tried: 4.3.46 on Arch Linux and 4.1.2 on CentOS 6.8. This is getting weirder: I've found I can replicate the behaviour you are getting Reuti, if I first do this command: unset COMMAND_PROMPT If I want to go back to the behaviour

Re: break no longer breaks out of loops defined in an outer context

2017-02-28 Thread Chet Ramey
On 2/28/17 3:10 PM, Stephane Chazelas wrote: > There was a related discussion on the Austin group mailing list > back in May last year: > > http://permalink.gmane.org/gmane.comp.standards.posix.austin.general/12614 > > Just my personal opinion, but I think I'd rather the spec had > been updated

Re: break no longer breaks out of loops defined in an outer context (was: Bug????)

2017-02-28 Thread Stephane Chazelas
2017-02-28 19:43:11 +0100, tarot: > Gr! it is not a bug!!! > > > xx. Fixed a bug that could allow `break' or `continue' executed from shell > functions to affect loops running outside of the function. > > My BIG script doesn't work with bash-4.4 > There was a related discussion on

Re: Bug ???????????

2017-02-28 Thread Chet Ramey
On 2/28/17 1:43 PM, tarot wrote: > Gr! it is not a bug!!! It is a bug, but if you rely on the previous behavior, you can set your shell's compatibility level to 4.3 (BASH_COMPAT=4.3) and get the behavior you want. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer

Bug ???????????

2017-02-28 Thread tarot
Gr! it is not a bug!!! xx. Fixed a bug that could allow `break' or `continue' executed from shell functions to affect loops running outside of the function. My BIG script doesn't work with bash-4.4

semicolon not added to history items when final line of compound list ends with a comment

2017-02-28 Thread Grisha Levit
Usually a multi-line command gets added to the history list with semicolons added in the requisite places, i.e: $ f() { > : > } $ fc -ln -1 f() { :; } However, if the final line is a comment, the semicolon is not added, making the history item an invalid command: $ f() {

Re: Why two separate option namespaces?

2017-02-28 Thread Stephane Chazelas
2017-02-27 16:18:46 -0500, Chet Ramey: > On 2/27/17 11:50 AM, Martijn Dekker wrote: > > > So basically you're saying that, for options without a single-letter > > equivalent, "-o" options are those that are either POSIX or that you > > think should be POSIX? But then that distinction is more polit

Re: "Variation" in Command Substitution Behaviour

2017-02-28 Thread Reuti
> Am 28.02.2017 um 14:21 schrieb Reuti : > > Hi, > >> Am 28.02.2017 um 11:00 schrieb Andreas Schwab : >> >> On Feb 28 2017, Geoff Hull wrote: >> >>> If I "source" the attached file (i.e. ". test_aliases") in a bash session, >>> then run the following: >>> >>> assemble_fam1 >>> assemble_fam2

Re: "Variation" in Command Substitution Behaviour

2017-02-28 Thread Reuti
Hi, > Am 28.02.2017 um 11:00 schrieb Andreas Schwab : > > On Feb 28 2017, Geoff Hull wrote: > >> If I "source" the attached file (i.e. ". test_aliases") in a bash session, >> then run the following: >> >> assemble_fam1 >> assemble_fam2 >> say_families >> >> I see the following output: >> >>

Re: "Variation" in Command Substitution Behaviour

2017-02-28 Thread Andreas Schwab
On Feb 28 2017, Geoff Hull wrote: > If I "source" the attached file (i.e. ". test_aliases") in a bash session, > then run the following: > > assemble_fam1 > assemble_fam2 > say_families > > I see the following output: > > Flintstones=wilma:bam-bam:fred > Rubbles=barney It seems like the shell is