Hello,
This patch fixes a bug in power in bc; 0 to any negative power should
be an error, but bc returns 0. This bug is my bad.
Gavin Howard
From 4aab9295913d8fcf7f3082d51b97b8b679655379 Mon Sep 17 00:00:00 2001
From: Gavin Howard
Date: Mon, 10 Jun 2019 19:52:37 -0600
Subject: [PATCH] bc: fix a
On 6/10/19 3:56 PM, enh wrote:
> thanks.
>
> much lower priority for me (and i'm volunteering to fix it), but...
> what should i do about the mac here?
Sigh, sounds like signames[] needs to move to portability.c.
> #if around the
> linux-only/mac-only signals (SIGPOLL is linux-only, SIGEMT is
>
okay, so with the -true/-false patch i can build AOSP with toybox
find. but i still get those warnings i mentioned years (?) ago but
only this morning actually have chance to dig into...
add something like this to tests/find.test:
+ln -s does-not-exist dir/dangler
+ln -s looper dir/looper
+testin
Used near the end of the AOSP build. Almost there!
(This patch also fiddles with the help text to be able to slip the new
options in without requiring so much extra space.)
---
tests/find.test | 3 +++
toys/posix/find.c | 43 ---
2 files changed, 27 inse
thanks.
much lower priority for me (and i'm volunteering to fix it), but...
what should i do about the mac here? #if around the
linux-only/mac-only signals (SIGPOLL is linux-only, SIGEMT is
mac-only, for example).
also -- something i didn't know until just now -- it turns out that
the mac doesn't
On 6/10/19 11:20 AM, enh wrote:
> On Mon, Jun 10, 2019 at 9:17 AM enh wrote:
>>
>> chet ramey replied
>> (https://www.mail-archive.com/austin-group-l@opengroup.org/msg04071.html)
>> that this has actually been changed to "undefined" in the
>
> [grr, stupid gmail --- why is there even a keyboard s
On 6/10/19 10:23 AM, enh via Toybox wrote:
> ping?
Applied.
> -*-
>
> i did think of a way we could maybe add a test for the real-time
> signals: collect the value from `kill -l SIGRTMAX` and check that
> `kill -l SIGRTMAX-1` is `$((sigrtmax - 1))`. (you might think that
> SIGRTMIN/SIGRTMAX are
Remove the existing link before trying to re-create, passing the test.
Add -p to the -r test as a regression guard, portage calls cp with both.
>From fa5e8e861171cd89b7fc4e5423c8ce3bafc93d3f Mon Sep 17 00:00:00 2001
From: makepost
Date: Mon, 10 Jun 2019 16:29:10 +
Subject: [PATCH] Fix cp -r di
https://www.phoronix.com/scan.php?page=news_item&px=TTY-Keyboard-Status-Request-RFC
On Sun, May 19, 2019 at 12:36 PM Rob Landley wrote:
>
> On 5/19/19 11:36 AM, Robert Thompson wrote:
> > When you need CTRL-\, you *really* need it...
>
> I haven't had CTRL-\ do anything ctrl-C doesn't this decade
On Mon, Jun 10, 2019 at 9:17 AM enh wrote:
>
> chet ramey replied
> (https://www.mail-archive.com/austin-group-l@opengroup.org/msg04071.html)
> that this has actually been changed to "undefined" in the
[grr, stupid gmail --- why is there even a keyboard shortcut for send,
and why is it one that's
chet ramey replied
(https://www.mail-archive.com/austin-group-l@opengroup.org/msg04071.html)
that this has actually been changed to "undefined" in the
On Mon, Jun 10, 2019 at 8:41 AM enh wrote:
>
> dash, ksh, mksh, and zsh all agree with POSIX. seems like bash is the
> exception (so POSIX is at l
dash, ksh, mksh, and zsh all agree with POSIX. seems like bash is the
exception (so POSIX is at least "right" in their limited sense of
"describe existing behavior").
i've forwarded a version of this question to the POSIX mailing list,
since there are few things that they like to argue about more
ping?
-*-
i did think of a way we could maybe add a test for the real-time
signals: collect the value from `kill -l SIGRTMAX` and check that
`kill -l SIGRTMAX-1` is `$((sigrtmax - 1))`. (you might think that
SIGRTMIN/SIGRTMAX are constants, but SIGRTMIN varies based on how many
real-time signals
13 matches
Mail list logo
