Re: printf -u "$fd"?

[Zachary Santer]

On Mon, May 20, 2024 at 3:03 PM Chet Ramey <chet.ramey@case.edu> wrote:
>
> On 5/17/24 10:53 PM, Zachary Santer wrote:
>
> > So here's another tangent, but has it been considered to add an option
> > to the printf builtin to print to a given file descriptor, rather than
> > stdout? If printing to a number of different file descriptors in
> > succession, such an option would appear to have all the same benefits
> > as read's -u option.
>
> It doesn't actually save anything; it's just syntactic sugar. Since
> `printf' uses stdio internally (as opposed to `read', which uses the
> supplied file descriptor directly), you're still going to have to dup2
> it internally somewhere. dprintf could do some of the work here, and bash
> has a replacement for systems where it's missing, but that's more than I
> want to change before bash-5.3 comes out. Maybe after that.

I was wondering what the relationship between the devel and master
branches was. I saw that you turned MULTIPLE_COPROCS=1 on by default
under devel, but haven't touched the somewhat more substantial changes
that sounded forthcoming, from that whole conversation. So I take it
MULTIPLE_COPROCS=1 will be enabled in bash-5.3 but other potential
changes would come later?

Do you keep a list of TODOs and things under consideration somewhere?