On Fri, Mar 07, 2025 at 02:34:32PM +0100, Martin Buck wrote: > On Wed, Mar 05, 2025 at 10:44:45AM +0100, Andreas Tille wrote: > > Inside the Tiny Tasks Matrix channel наб asked: > > "isn't mbuffer the same as buffer but better?" > > So I'm all for simply dropping buffer and recommending mbuffer instead (is > that important enough for the "Noteworthy obsolete packages" section in the > release notes?). Ideally we could provide buffer with mbuffer, but this may require a wrapper; just glancing at the manuals I see a different default size and no -S; this could just be as simple as a getopt(1) loop however.
...actually mbuffer's default seems to be -S $blocksize (with a different output format, which is very busy); there's -q to disable it, but no option to change the logged increments. And there's no way AFAICT to disable config file loading. So no dice without significant mbuffer patching.
signature.asc
Description: PGP signature
