Re: Redoing the code in /bin/sh to handle the issues in PR bin/48875

2018-08-19 Thread Robert Elz
Date:Sat, 18 Aug 2018 08:00:40 -0500 From:"J. Lewis Muir" Message-ID: <20180818130040.ga1...@tuna.imca.aps.anl.gov> | I see your point. Yes, this seems too long. Maybe it would be more | appropriate in the POSIX sh shell book you were planning to write. :-) Yea

Re: Redoing the code in /bin/sh to handle the issues in PR bin/48875

2018-08-18 Thread J. Lewis Muir
On 08/18, Robert Elz wrote: > Does this actually help, or is all this text just making it less likely that > the average script writer will ever read any of it? I see your point. Yes, this seems too long. Maybe it would be more appropriate in the POSIX sh shell book you were planning to write.

Re: Redoing the code in /bin/sh to handle the issues in PR bin/48875

2018-08-17 Thread Robert Elz
Date:Fri, 17 Aug 2018 11:37:18 -0500 From:"J. Lewis Muir" Message-ID: <20180817163717.ga21...@tuna.imca.aps.anl.gov> | I think this sentence would read better if it used the same verb tense Thanks, that is the kind of improvement I was looking for (since I don't of

Re: Redoing the code in /bin/sh to handle the issues in PR bin/48875

2018-08-17 Thread J. Lewis Muir
On 08/17, Robert Elz wrote: > I'd appreciate any suggestions for improvements, particularly ways > to convey the information included in a more succinct form. > > This is the (new) text I currently have ... > > Note that if a command substitution includes commands to be run in the > bac

Redoing the code in /bin/sh to handle the issues in PR bin/48875

2018-08-17 Thread Robert Elz
Some (or many) of you may be aware (and if not, please read the PR) that the code added in 2016 to deal with PR bin/48875 was never really correct - it just had not, until recently, caused anyone any problems so it had just been sitting there, doing its thing, and bothering no-one really, until jus