On 3/12/24 12:24, enh wrote:
> On Tue, Mar 12, 2024 at 8:45 AM Rob Landley wrote:
>>
>> Hello from Minneapolis: https://mstdn.jp/@landley/112078501045637288
>>
>> Still _really_ fried from my move, but at least chipping away at the email
>> backlog...
>
> at least it's the same timezone :-)
On 2024-03-12 10:24:19, enh via Toybox wrote:
> On Tue, Mar 12, 2024 at 8:45 AM Rob Landley wrote:
> >
> > Hello from Minneapolis: https://mstdn.jp/@landley/112078501045637288
> >
> > Still _really_ fried from my move, but at least chipping away at the email
> > backlog...
>
> at least it's the
On Tue, Mar 12, 2024 at 8:45 AM Rob Landley wrote:
>
> Hello from Minneapolis: https://mstdn.jp/@landley/112078501045637288
>
> Still _really_ fried from my move, but at least chipping away at the email
> backlog...
at least it's the same timezone :-)
> On 3/11/24 12:27, enh wrote:
> > On Fri,
Hello from Minneapolis: https://mstdn.jp/@landley/112078501045637288
Still _really_ fried from my move, but at least chipping away at the email
backlog...
On 3/11/24 12:27, enh wrote:
> On Fri, Mar 8, 2024 at 5:43 PM Rob Landley wrote:
>>
>> I remember when the xprintf() family would do a flush
On Fri, Mar 8, 2024 at 5:43 PM Rob Landley wrote:
>
> I remember when the xprintf() family would do a flush and check for errors
> each
> write. That's why code like:
>
> dprintf(1, "%c", pad if (width) xputs(ss+(width>ctimelen ? 0 : width-1));
> if (yy>=3) dprintf(1,
I remember when the xprintf() family would do a flush and check for errors each
write. That's why code like:
dprintf(1, "%c", padctimelen ? 0 : width-1));
if (yy>=3) dprintf(1, "\r\n");
Was allowable.
I also remember when we had an xflush() that would catch errors if stdout
---
toys/other/watch.c | 1 +
1 file changed, 1 insertion(+)
0001-watch-flush-the-buffer-each-round.patch
Description: Binary data
___
Toybox mailing list
Toybox@lists.landley.net
http://lists.landley.net/listinfo.cgi/toybox-landley.net
