Re: [hackers] [sbase][PATCH] Minor optimizations for 'yes'

2019-06-27 Thread Michael Forney
On 2019-06-27, aidanwillie0317 wrote: > Or, even simpler: Thanks, this looks good. Only a couple minor comments. Could you update the man page to reflect the fact that now only one string is supported? > --- > yes.c | 10 +++--- > 1 file changed, 3 insertions(+), 7 deletions(-) > > diff

[hackers] [dwm][PATCH] fix status bar width in buttonpress

2019-06-27 Thread ornx
--- dwm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dwm.c b/dwm.c index 4465af1..60c2a24 100644 --- a/dwm.c +++ b/dwm.c @@ -439,7 +439,7 @@ buttonpress(XEvent *e) arg.ui = 1 << i; } else if (ev->x < x + blw) click = ClkLtSymbol; - else if (ev->x > selmon->ww -

Re: [hackers] [sbase][PATCH] Minor optimizations for 'yes'

2019-06-27 Thread aidanwillie0317
> What about /dev/zero? I really overengineered this benchmark, and I completely forgot about that. > In fact, since yes(1) is a non-standard utility, I wonder if we should > even bother supporting multiple arguments. It looks like some BSD > implementations only repeat the first argument. > >

Re: [hackers] [sbase][PATCH] Minor optimizations for 'yes'

2019-06-27 Thread Quentin Rameau
Hello, > So, we could make this as simple as > > s = argc > 1 ? argv[1] : "y"; > for (;;) > puts(s); > > >> I think I'd prefer > >> > >>for (;;) > >>puts("y"); > >> > >> here. > > Originally, I had a puts(3) call there, but this decreased the