Re: Examples of concurrent coproc usage?

On 4/1/24 3:24 PM, Chet Ramey wrote: On 3/14/24 5:58 AM, Carl Edquist wrote: But you can create a deadlock without doing anything fancy. Well, *without multi-coproc support*, here's a simple wc example; first with a single coproc:  $ coproc WC { wc; }  $ exec {WC[1]}>&-  $ rea

Re: Examples of concurrent coproc usage?

On 3/14/24 5:58 AM, Carl Edquist wrote: But you can create a deadlock without doing anything fancy. Well, *without multi-coproc support*, here's a simple wc example; first with a single coproc: $ coproc WC { wc; } $ exec {WC[1]}>&- $ read -u ${WC[0]} X $ echo $X 0

Re: Manual: clarify what POSIX stands for

On 3/31/24 8:47 PM, Martin D Kealey wrote: On Thu, 25 Jan 2024, 20:04 Alan Urmancheev, wrote: Currently, Bash's manual definitions section mentions POSIX, but doesn't explain what that abbreviature stands for ... I think that abbreviatures can be confusing, especially when you don't get

Re: Bug tracking

On 4/1/24 5:30 AM, Koichi Murase wrote: Perhaps bug tracking could be migrated to a more modern system? I think a more realistic solution for GNU is to improve Savane, which is also an open-source project: https://savannah.nongnu.org/projects/administration/ That is a GNU project decision, a

Re: Bug tracking

On 3/31/24 8:34 PM, Martin D Kealey wrote: On Mon, 11 Dec 2023, 05:19 Chet Ramey, > wrote: On 11/30/23 5:18 AM, Martin D Kealey wrote: > If there's a bug tracking system beyond "threads in a mailing list", I'd > like to know how I can get access t

Re: [PATCH 06/13] lib/readline/doc/history.3: Drop microtypography.

On 3/28/24 5:11 PM, G. Branden Robinson wrote: Now that we're using a correct caret/circumflex/hat glyph on modern typesetters (and terminals with a Unicode repertoire), drop the thicket of partial-line motion and type size-altering escape sequences, certain to frighten and confuse any unfrozen c

Re: Bug tracking

2024年4月1日(月) 9:35 Martin D Kealey : > On Mon, 11 Dec 2023, 05:19 Chet Ramey, wrote: > > On 11/30/23 5:18 AM, Martin D Kealey wrote: > > > If there's a bug tracking system beyond "threads in a mailing list", I'd > > > like to know how I can get access to it. > > > > https://savannah.gnu.org/support