![](https://seccdn.libravatar.org/avatar/247f3737bfdd07c80a5411399e9a504c.jpg?s=120&d=mm&r=g)
Randall R Schulz wrote:
CTRL-C is not usually considered a "normal" way to terminate a program.
Instead, it is abortive and may lead to the program to fail to clean up and shut down properly (though that would be considered rather poor Unix / Linux programming form).
A program that fails to clean up and shut down properly (or take some other appropriate action according to its specification) is buggy, pure and simple.
q is the way to ask this particular process nicely. But there's no effective difference between q and CTRL-C in this case, AFAIK.
In this case. But is not a good habit to develop to use CTRL-C (SIGINT) to routinely shut down an application.
Why is it not a good habit? What problems does it cause? Doing it routinely is a good way of making sure that programs are free of such bugs. Just as typing %8888f into text fields is always worth a try :) Cheers, Dave