John Little wrote:
> On Monday, August 6, 2018 at 10:21:03 AM UTC+12, joshudson wrote: > > vim gets very confused when it gets a TSTOP, TTIN, or STOP signal and later > > a CONT signal. > > I see this in vim 8.1.0239, sending SIGSTOP. The pseudo-terminal is > in line mode; typing :!echo<cr> causes vim to reset it. Using > > stty -F /dev/pts/<number> raw > > then ctrl-L in vim resets it too. > > >I remember being able to do this in classic vi from ages ago. > > This perked my interest, because surely I used to do this a lot every > day with actual terminals. I even built vim 6.4 and 5.8 to check them > out, but their behaviour is the same (in my KDE with plasma 5, but > also in the Linux console). > > Now :suspend and ctrl-Z work, so now I think that's what I used to do > all the time back then. So it's only sending SIGSTOP from somewhere > else that gives trouble. Sometimes I get junk back in the shell, f.ex. > " xM P. xM#P.", that my shell thinks I've typed. > > Weird that no-one bothered about it then. There was a related problem > fixed in Vim-7.2.130 that was due to a race condition, so maybe 2018 > hardware has brought this out. See mch_suspend() in os_unix.c to see > the details; maybe vim could use this if it gets a SIGCONT it's not > expecting. Yes, we can do that. I'll make a patch. It won't be perfect, depending on the state Vim is in, but should work in many cases. > However, the best approach might be, don't do that. IIUC SIGSTOP > can't be caught, blocked, or ignored and if vim has the X selection > other processes that ask for it will hang. Exactly. -- Time flies like an arrow. Fruit flies like a banana. /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
