Oops, my mistake. Got some terms mixed up a little there. Yes, every time I command substitution, I meant process substitution. So that release note for "Rewrote the command substitution" most likely nothing to do with this. ________________________________ From: Robert Elz <k...@munnari.oz.au> Sent: Tuesday, October 18, 2022 7:09 PM To: Andrew Neff <andrew.n...@visionsystemsinc.com> Cc: bug-bash@gnu.org <bug-bash@gnu.org> Subject: Re: caller returns wrong line number in command substitution
There are no command substitutions in any of your examples. A command substitution is what you get with $( ) (or if you really like obsolete syntax for some reason, ``). What you're showing is process substitution. This has nothing to do with whether or not there is an issue here that's worth fixing however - but bash's management of line numbers has always been "close enough" rather than "accurate". kre
