Conversation

Notices

1. Embed this notice
   Chris Siebenmann (cks@mastodon.social)'s status on Thursday, 20-Mar-2025 01:45:00 JST Chris Siebenmann

   in reply to

   • Julia Evans

   @b0rk I ticked off 'the shell' in my set of answers because of technical knowledge: a shell with readline handling is handling Ctrl+C itself when you're editing a command line. Many shells/readline environments will react to Ctrl+C this way by 'interrupting' the command line you're editing and giving you a new top level prompt (which is handy if eg you're writing a multi-line 'for' or 'while' or etc and change your mind; you can Ctrl+C to throw the entire thing away).

   • Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Julia Evans (b0rk@social.jvns.ca)'s status on Thursday, 20-Mar-2025 01:45:01 JST Julia Evans

     follow up: for folks who replied to "who's in charge of making Ctrl+C work in the terminal" with "the shell”, why did you say that?

     I'm much more interested in answers that you're not 100% sure about than "right" answers

     (also please don't correct people who say something you think is "wrong”)

     (2/?)