This comment was originally written by @Fox32

My fault, it seems to work on Windows. But I have still issueson OSX and Linux. I use the following test program:

import 'dart:io';

void main(List<String> arguments) {
  stdin.echoMode = false;
  // Case 1: Not reseted
  return;
  // Case 2: Not reseted
  throw new ArgumentError();
  // Case 3: Not reseted
  exit(0);
  // Case 4, using Ctrl+C to exit the program: Reseted!
  new Future.delayed(const Duration(milliseconds: 50000), () {
   print('test');
  });
}

Added Area-IO, Triaged labels.

I just tested this in python where I see the same behavior with http://docs.python.org/2/library/curses.html.

I'm not sure what the right thing to do is. While I agree that it's unexpected, it's needed if a person wants to write a tool that simply disables echo and returns.

This comment was originally written by @Fox32

It would be possible to reset it myself on normal exit as I only have two exit points. On abnormal exit I could use the Zone interfaces to catch all unhandled errors and disable it. But a global handler is annoying during development. Something like a global finally block isn't available right?

Not that I'm aware of. I'll discuss with the library team if they have any suggestions for this scenario.

So, we're in the process of adding some ways of recovering, by running the program in a child isolate. However, we are still early in the process and the API is not yet in place.

Have you tried encapsulating the program in another process?

This comment was originally written by @Fox32

Thanks for that idea, I haven't thought about another process or isolate yet. I will look into that.

This comment was originally written by @Fox32

I checked the possible solutions:
A own process is not "possible" as it would be very difficult to work with during development. Perfect would be an isolate based solution. My first steps work well for normal exit, but the isolate library seems to miss a good way of handling crashes in the child isolate (maybe a zone that sends back a message?). After my first steps with isolates, I thought it would be nice to name isolates for development, that would make debugging much easier while working with multiple isolates (Something like http://msdn.microsoft.com/en-us/library/xcb2z8hs.aspx, only available if debugger enabled?). Here is my current code:

void main(List<String> arguments) {
  final previousEchoMode = stdin.echoMode;

  Isolate.spawn(run, arguments).then((i) {
    final rp = new ReceivePort();

    i.addOnExitListener(rp.sendPort);

    return rp.single.then((_) {
      // Not called if the isolate terminates in a abnormal way (crash)
      stdin.echoMode = previousEchoMode;
    });
  });
}

void run(List<String> arguments) {
 // My old main code...
}

Removed Area-IO label.
Added Library-IO label.

Issue #17746 has been merged into this issue.

This comment was originally written by @Fox32

I just want to mention that is now possible to workaround this issue with addOnExitListener, works fine.

I think addOnExitListener is the expected workaround.

@lrhn or @zanderso - please reopen if you think we should handle resetting echo mode automatically.