Ctrl + Break and Ctrl + C are treated slightly differently by Windows. Ctrl + Break is always a signal, but an application can override the functionality of Ctrl + C.
Please see https://docs.microsoft.com/en-us/windows/console/ctrl-c-and-ctrl-break-signals I’ve dealt with this issue many times in the past (in other applications) in which I tried Ctrl + C but got nowhere. As such, I prefer the current behavior. Your Surface 4 keyboard simply doesn’t have a Break or Pause key. Either try getting another keyboard, use the Pause on the on screen keyboard, use a 3rd party utility to map the keystroke, or just use Ctrl + C. Many people have complained about this issue, but I don’t consider it a Django issue. From: django-developers@googlegroups.com <django-developers@googlegroups.com> On Behalf Of wi...@wsvincent.com Sent: Monday, June 21, 2021 3:10 PM To: Django developers (Contributions to Django itself) <django-developers@googlegroups.com> Subject: CTRL-BREAK still make sense on Windows for `runserver`? Hi all, Is the Pause/Break key still a thing on Windows keyboards? My new Surface 4 doesn't even have such a key and I think this applies to many new Windows keyboards as well. I ask because the runserver.py command <https://us-east-2.protection.sophos.com?d=github.com&u=aHR0cHM6Ly9naXRodWIuY29tL2RqYW5nby9kamFuZ28vYmxvYi9jYTk4NzI5MDU1NTkwMjZhZjgyMDAwZTQ2Y2RlNmY3ZGVkYzg5N2I2L2RqYW5nby9jb3JlL21hbmFnZW1lbnQvY29tbWFuZHMvcnVuc2VydmVyLnB5&i=NWVjN2YxNzUxNGEyNzMxNmMyMGRkZGU1&t=YTlxOTdKamhFNC9ub0tLTWcwVDZJeVZ3THZieWdGUHNnakd4dzl1N2I0cz0=&h=1f6ccd5d41ea42feafd897fba33f5f12> currently has `CTRL-BREAK` if Windows32 or `CONTROL-C` for everything else, like Mac/Linux. Seems this could be just standardized to `CONTROL-C` no? -Will -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com<mailto:django-developers+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/ee88cce3-3f7e-4ca8-b2af-e1bc4b1fe8c4n%40googlegroups.com<https://us-east-2.protection.sophos.com?d=google.com&u=aHR0cHM6Ly9ncm91cHMuZ29vZ2xlLmNvbS9kL21zZ2lkL2RqYW5nby1kZXZlbG9wZXJzL2VlODhjY2UzLTNmN2UtNGNhOC1iMmFmLWUxYmM0YjFmZThjNG4lNDBnb29nbGVncm91cHMuY29tP3V0bV9tZWRpdW09ZW1haWwmdXRtX3NvdXJjZT1mb290ZXI=&i=NWVjN2YxNzUxNGEyNzMxNmMyMGRkZGU1&t=UUJCeFNYL2NLSkU4S0E4UWJaa29JaXpCRTcrVHFUY3pHNUtzTFhYSGJ2Zz0=&h=1f6ccd5d41ea42feafd897fba33f5f12>. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/602088ed84714747a4b095939e18cd93%40Exchange.ISS.LOCAL.
