On Monday 23 September 2002 12:50, Stuart Langridge wrote: > David Pashley spoo'd forth: > > On Monday 23 September 2002 3:49 am, Hendrik Sattler wrote: > >> Am Montag, 23. September 2002 03:40 schrieb Donald R. Spoon: > >> > Hendrik Sattler wrote: > >> > > sometimes I accidently hit Ctrl-S instead of Shift-S. This seems to > >> > > disable the ability to do any keyboard input to that session. So > >> > > what's wrong? How can I reenable input without closing the window > >> > > and opening a new one? > >> > > >> > Try hitting Ctrl-Q and see what happens.... > >> > >> Thanks, that really did it. Is there a way to disable this behaviour? > > > > This is dealt with by the same thing that deals with ctrl-C and ctrl-\. > > AIUI that is the kernel. They are signals SIGSTOP and SIGCONT iirc. So > > basically you don't have much chance of stopping it. > > Look at the stty command, in particular "stty start" and "stty stop", > which define the stop and start keypresses. You can change what each of > these are (so you can change the start character from ^S to something > else), although I have no idea whether you can use a "Rollen" key.
This has been addressed in KDE 3.1 - you can enable or disable Ctrl+S/Ctrl+Q. Regards, Malcolm -- KDE Proof Reading Team KDE GB English Translation Team
