Generally when I want to quit an iex session I use the double control-c dance. For unknown reasons this refused to work earlier today but I am not getting into that. Because of it though I tried System.halt/1 to exit the session and that worked. Is there a difference between the 2 methods? Else …

That combination seems to be bound to tmux, it jumps back to the last pane.

Maybe the normal close (ctlr double c) uses stop instead, which is meant to be less aggressive than System.halt . There may have been something preventing the sequential shutdown of the runtime?

Definitely not System.stop, when I do that I see a lot of errors/warnings I do not see with the ctrl-c nor System.halt

Here’s another tip courtesy of the System module. You know “that” error…? ** (RuntimeError) could not compile application: my_app. You must restart your server after changing the following files: config/dev.exs (phoenix 1.7.12) lib/phoenix/code_reloader/server.ex:236: Phoenix.CodeReloader.Se…

The first CTRL-C gets you into the break menu which gives you a few diagnostic options. When you then press q or a and ENTER, or simply another CTRL-C you are effectively doing a System.halt(0) call. CTRL-\ bypasses the break menu altogether and quits. System.stop(0) is more graceful than System.h…

I always assumed that System.halt was more aggressive in that sense. I mean, System.stop takes longer, so it must be exiting more gracefully! That being said, I always exit by double-pressing Ctrl + C, and I’ve never had any issues with ports being left open, or any bad side effects like that. Wou…

There are scenarios where CTRL-C twice could take down daemons running on a remote node. Not much harm if you are just messing around locally. However, if we are talking best practices, you’d probably want CTRL-G to bring up the User switch command menu, followed by q. Try h to see the options avail…

Elixir Programming Language Forum

Quitting an iex session - any difference between System.halt/1 & CTRL-C?

Questions & Help Questions

sodapopcan May 9, 2024, 11:31am 6

WHOA! I had no idea that worked.