** exception exit: noconnection
Wed Dec 4 17:41:45 CET 2019
I got mostly tripped up on not being able to wrap the code in a try-catch and be able to catch it. Therefore I think it would make sense to print something else when the shell actually receives an exit signal so users can understand that they are special somehow.
> On 4. Dec 2019, at 16:41, Roger Lipscombe <roger@REDACTED> wrote:
> On Wed, 4 Dec 2019 at 15:06, Adam Lindberg <hello@REDACTED> wrote:
>> It does receive an exit signal, and then dies because of it, no?
> Sorry. Lack of precision: it's not *trapping* exit signals by default,
> so it gets default-killed. The process that owns the shell process
> traps *that*, but can't tell the difference, so emitting a different
> message for the two cases might not be that simple.
More information about the erlang-questions