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

Groups > gnu.bash.bug > #15504 > unrolled thread

Re: Command grouping

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Command grouping Mischa Baars <mjbaars1977.bug-bash@cyberfiber.eu> - 2019-10-13 10:09 +0200

#15504 — Re: Command grouping

On Sat, 2019-10-12 at 10:42 -0400, Chet Ramey wrote:
> 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.
> 

Hi Chet,

The bash manual page tells us that is the default value, nothing special.

I was trying to remove the whitespace, such that whitespaces are allowed in project directory names, as was considered the default scenario as far as I know.

Mischa.

[toc] | [standalone]

Back to top | Article view | gnu.bash.bug

csiph-web