Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #15503

Re: Command grouping

From Chet Ramey <chet.ramey@case.edu>
Newsgroups gnu.bash.bug
Subject Re: Command grouping
Date 2019-10-12 10:42 -0400
Organization ITS, Case Western Reserve University
Message-ID <mailman.398.1570891354.9715.bug-bash@gnu.org> (permalink)
References <acdb21fe37e928c2063c95ec1d013fe695e3bdf1.camel@cyberfiber.eu> <06070f12-033d-0736-1733-a035629104cd@case.edu>

Show all headers | View raw


On 10/12/19 9:02 AM, Mischa Baars wrote:
> Hi,
> 
> Perhaps to better have a look at this mail, than the previous mail.
> 
> In trying to group commands, in this case compiler commands, I found some peculiarities while trying different combinations of the 'Internal Field Separator'
> and the 'Parameter Expansion' operator ${parameter@P}.

I haven't looked at this in any depth, but you should realize that running

declare IFS=$(printf ' \t\n')

will result in IFS being set to space and tab, since command substitution
removes the trailing newline. Maybe that will make a difference.


-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread


Thread

Re: Command grouping Chet Ramey <chet.ramey@case.edu> - 2019-10-12 10:42 -0400

csiph-web