Personally I don't have any problem with 800 kB == 8 GB or 104857600
KiB == 100 GiB, but it's not as if having nice round power-of-two numbers
really matters in *this* case, where 107500 KiB is close enough to 1
TiB. But I guess not everyone is as comfortable with mental arithmetic.
On Thu
Christian Convey writes:
> When setting memory-size limits via "ulimits", users have to manually
> convert from their intuitive units.
>
> E.g., for limiting virtual memory to 8 gigabytes, the invocation is "ulimit
> -v 8388608", rather than something like "ulimit -v 8gb".
>
> If I were to submit
On Tue, 27 Feb 2024 at 18:48, Oğuz wrote:
> On Tuesday, February 27, 2024, Martin D Kealey
> wrote:
>
>> I've been thinking for a while now that POSIX made a mistake when it
>> permitted ';;' before the closing 'esac'.
>>
>
> I think that decision was made before POSIX. Besides it's handy when
>
On 2/27/24 7:25 PM, Seth Sabar wrote:
Hi,
I'd like to report a bug with the *--pretty-print* feature of bash. When I
run the following script:
*coproc sleep 5*
the pretty-printed result is
*coproc COPROC* sleep 5
Thanks for the report. This issue was fixed back in December as the
result of
