* Ivan Tham 2017-05-11 03:58
> I prefer it to close automatically after a timeout AND interactively with:
>
> timeout 5 read
I understand this, but for me it limits your options for no reason. The
only benefit is that you don't have open terminals for each downloaded
file. I fouund out this
Hi Pickfire,
> I prefer it to close automatically after a timeout AND interactively
> with:
>
> timeout 5 read
Thanks for the suggestion, but timeout is GNU-specific, and I actually
find the mix of both pretty redundant and even less supple.
s...@mailless.org wrote:
> Hi,
>
> I chime in again:
>
> I think it's definitely the right thing to make it interactive, rather than
> sleep.
>
> I found it very beneficial to go a step further: rather than just asking for
> confirmation with `read`, I drop the user in a shell, after the
> I found it very beneficial to go a step further: rather than just
> asking for confirmation with `read`, I drop the user in a shell,
> after the download is complete. They see what file was downloaded, a
> `pwd` gives them even more context and they can right away do
> whatever they intended
Hi,
I chime in again:
I think it's definitely the right thing to make it interactive, rather than
sleep.
I found it very beneficial to go a step further: rather than just asking for
confirmation with `read`, I drop the user in a shell, after the download is
complete. They see what file was
