Re: Request For Enhancement - TID variable

Daniel Colascione : > Are you sure that'd help? Parallel runs bash in a bunch of subprocesses, so > looking at PID would suffice to distinguish jobs. Are you sure you weren't > seeing an invariant PID because you were letting the PID variable expansion > happen too early? The $$ is inside the

Re: Fwd: Don't set $?=130 when discarding the current command line (not run yet) with CTRL-C?

On 12/23/19 9:54 PM, Clark Wang wrote: > Hi Chet, > > On Fri, Nov 22, 2019 at 12:02 AM Chet Ramey > wrote: > > On 11/20/19 9:27 PM, Clark Wang wrote: > > It's quite common for people to press CTRL-C to discard the current > command > > line. This is

Re: Request For Enhancement - TID variable

On Dez 26 2019, Eric S. Raymond wrote: > RFE: bash should have a TID varuable that returns the vakue of gettid(2). Bash doesn't use threads, so $TID will always be the same as $BASHPID. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5

Re: Request For Enhancement - TID variable

On 12/26/19 7:37 AM, Eric S. Raymond wrote: In attempting to use GNU parallel, with some bash scripts, I discovered I had a problem with tempfile collisions due to all of the thread having the same PID. I was able to come up with a workaround, but... RFE: bash should have a TID varuable that

Request For Enhancement - TID variable

In attempting to use GNU parallel, with some bash scripts, I discovered I had a problem with tempfile collisions due to all of the thread having the same PID. I was able to come up with a workaround, but... RFE: bash should have a TID varuable that returns the vakue of gettid(2). If the bash