On Sat, Nov 17 2018, Klemens Nanni wrote:
> On Sun, Nov 11, 2018 at 05:39:52PM +0100, Klemens Nanni wrote:
>> On Sat, Nov 03, 2018 at 09:01:33PM +0100, Klemens Nanni wrote:
>> > Closing stdin makes sense, but I still want to see error messages from
>> > the program I'm running. Since arbitrary
On Sun, Nov 11, 2018 at 05:39:52PM +0100, Klemens Nanni wrote:
> On Sat, Nov 03, 2018 at 09:01:33PM +0100, Klemens Nanni wrote:
> > Closing stdin makes sense, but I still want to see error messages from
> > the program I'm running. Since arbitrary progams can be run, keep both
> > stdout and
On Sat, Nov 03, 2018 at 09:01:33PM +0100, Klemens Nanni wrote:
> Closing stdin makes sense, but I still want to see error messages from
> the program I'm running. Since arbitrary progams can be run, keep both
> stdout and stderr open so users get a chance to actually notice program
> failure or
