Bug#306043: bash executable completion doesn't work if there is a space in the executable path

2024-04-05 Thread Gioele Barabucci
Control: found -1 5.2.21-2 Control: tags -1 upstream X-Debbugs-CC: bug-bash@gnu.org On Sat, 23 Apr 2005 15:20:19 -0700 Frederik Eaton wrote: Bash executable completion doesn't work if there is a space in the executable path. This issue is still partially present in current version of Bash. T

Re: [sr #111047] Value of BASHPID changes when inside a here-document

2024-04-05 Thread Chet Ramey
On 4/4/24 9:05 PM, Lawrence Velázquez wrote: Reproducing my comment [1] for the list: On Apr 4, 2024, at 5:57 PM, Richard Waite wrote: Does variable expansion for here-documents occur in a subshell? Sometimes. When a command requires forking (roughly speaking), its redirections (not just

Re: Scope change in loops with "read" built-in

2024-04-05 Thread Greg Wooledge
On Thu, Apr 04, 2024 at 08:39:51PM -0400, Dale R. Worley wrote: > To circumvent that, I've sometimes done things like > > exec 3<( ... command to generate stuff ... ) > while read VAR <&3; do ... commands to process stuff ... ; done > exec 3<- Please note that the syntax for closing a

Re: Scope change in loops with "read" built-in

2024-04-05 Thread Kerin Millar
On Thu, 04 Apr 2024 20:39:51 -0400 "Dale R. Worley" wrote: > "Linde, Evan" writes: > > In a loop constructed like `... | while read ...`, changes to > > variables declared outside the loop only have a loop local > > scope, unlike other "while" or "for" loops. > > Yeah, that's a gotcha. But it