this post was submitted on 29 Oct 2024
740 points (95.0% liked)

linuxmemes

21138 readers
721 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     

    Yes yes, I REALLY want to terminate that process and I am very sure about it too, ty.

    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 45 points 1 day ago

    Actually no, it's just that the programs on Linux usually accept SIGINT, SIGTERM, etc pretty gracefully. Some are even smart enough to handle it on a thread hang. SIGKILL is last resort.

    Lots of Windows applications like to ignore the close request because Windows doesn't have signals and instead you can only pass a window name to request exit which is the same as clicking the close button.

    So any hung software won't respond and you have to terminate it.