Re: midicat(1): use err(3)

On Wed, Nov 30, 2022 at 09:20:26AM -0600, Scott Cheloha wrote: > Couple related things: > > - Use err(3) everywhere. > > For many of these errors we are not currently printing the errno > string. Is there any reason not to do so? The errno string is > useful. > > - Set ifile/ofile to

Re: midicat(1): use err(3)

On Wed, Nov 30, 2022 at 08:55:45AM -0700, Todd C. Miller wrote: > On Wed, 30 Nov 2022 09:20:26 -0600, Scott Cheloha wrote: > > > Couple related things: > > > > - Use err(3) everywhere. > > > > For many of these errors we are not currently printing the errno > > string. Is there any reason

Re: midicat(1): use err(3)

On Wed, 30 Nov 2022 09:20:26 -0600, Scott Cheloha wrote: > Couple related things: > > - Use err(3) everywhere. > > For many of these errors we are not currently printing the errno > string. Is there any reason not to do so? The errno string is > useful. OK > - Set ifile/ofile to

midicat(1): use err(3)

Couple related things: - Use err(3) everywhere. For many of these errors we are not currently printing the errno string. Is there any reason not to do so? The errno string is useful. - Set ifile/ofile to "stdin"/"stdout" if the user passes in "-" to make the err(3) message a little