[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#34488: Add sort --limit, or document workarounds for sort|head error
From: |
Pádraig Brady |
Subject: |
bug#34488: Add sort --limit, or document workarounds for sort|head error messages |
Date: |
Sun, 3 Mar 2019 17:47:24 -0800 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 |
On 03/03/19 16:59, Pádraig Brady wrote:
> A summary of the all signal options in my local set now is:
>
> --block-signal[=SIG] block delivery of SIG signal(s) to COMMAND
> --unblock-signal[=SIG] unblock delivery of SIG signal(s) to COMMAND
> --default-signal[=SIG] reset handling of SIG signal(s) to the default
> --ignore-signal[=SIG] set handling of SIG signals(s) to do nothing
> --list-signal-handling list non default signal handling to stderr
I think we might be also able to remove --unblock-signal,
and just have --default-signal.
I.E. I don't think one would want to set default signal handling,
but leave a signal blocked? Also I don't think one would
want to unblock a signal, but leave it ignored?
At least not and the level of env just exec()ing a program.
Anyway if those weird cases are needed, they can be achieved
by combining the options.
The attached does that, leaving us with:
--block-signal[=SIG] block delivery of SIG signal(s) to COMMAND
--default-signal[=SIG] reset handling of SIG signal(s) to the default
--ignore-signal[=SIG] set handling of SIG signals(s) to do nothing
--list-signal-handling list non default signal handling to stderr
cheers,
Pádraig.
env-no-unblock.patch
Description: Text Data