On 4/13/19 3:54 AM, konsolebox wrote:
>
> shift "$(( n < $# ? n : $# ))"
Yep - thx!
--
Toralf
PGP C4EACDDE 0076E94E
On 4/13/19 9:42 AM, Toralf Förster wrote:
> Yep - thx!
Except, that I used the opposite:
min_days=${1:-5}
min_hours=${2:-12}
min_compl=${3:-3500}
shift "$(( $# < 3 ? $# : 3 ))"
setupargs="$@"
--
Toralf
PGP C4EACDDE 0076E94E
On 4/12/19 4:28 PM, Daniel Kahn Gillmor wrote:
> None of the other bourne-derived shells that i have tried have a builtin
> wait that waits on child processes that they didn't directly create.
> It's odd that bash 5.0 does this. I don't have any objection to the
> wait builtin waiting on coproces
On 3/28/19 8:01 AM, Tycho Kirchner wrote:
> Dear bash-maintainers,
> the *interactive* bash leaks (pipe-)file-descriptors when fast interrupts
> (SIGINT) occur. The bug occurs on all bash-versions tested (see below),
> including 5.0.2(1)-release.
I don't see any issue on Mac OS X.
What I get is y
On 4/11/19 4:41 PM, Benjamin Barenblat wrote:
> Bash Version: 5.0
> Patch Level: 3
> Release Status: maint
>
> Description:
> Silence pushd/popd output if executed with -q. This could also be
> achieved by executing them with 2>/dev/null, but -q avoids the
> extra open(2).
Than
Am 13.04.19 um 21:19 schrieb Chet Ramey:
On 3/28/19 8:01 AM, Tycho Kirchner wrote:
Dear bash-maintainers,
the *interactive* bash leaks (pipe-)file-descriptors when fast interrupts
(SIGINT) occur. The bug occurs on all bash-versions tested (see below),
including 5.0.2(1)-release.
I don't see an
On Sat, Apr 13, 2019 at 03:19:17PM -0400, Chet Ramey wrote:
> On 3/28/19 8:01 AM, Tycho Kirchner wrote:
> > the *interactive* bash leaks (pipe-)file-descriptors when fast interrupts
> > (SIGINT) occur. The bug occurs on all bash-versions tested (see below),
> > including 5.0.2(1)-release.
>
> I do
