Package: vim Version: 1:6.4-007+1 On a sufficiently slow machine, vim accumulates signals, which is tedious to have to deal with. Example:
I run some command which accesses the disk alot, causing vim in another xterm to become unresponsive for a couple seconds. During that period, I manage to give that xterm the focus, and attempt to background vim and continue work in the shell. So I hold down ^Z to background vim. When it finally backgrounds (around about the time the expensive command completes), it is "difficult" to foreground; entering fg 5 or whatever will bring up a flash of vim, and then it will apparently remember one of the pending sigstops, and immediately suspend itself. One has to enter the "fg" command potentially a large number of times before vim is actually usable. It isn't clear to me that this a actually a bug in vim, and not in bash or the kernel or something else; but the useful behaviour here would be for vim to "collapse" multiple pending SIGSTOPs into a single one...but vim isn't sending itself the SIGSTOP, then, is it...and SIGSTOP can't be ignored, right? So does this need to be reassigned somewhere? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
