On 2019-02-15, James McCoy wrote: > On Fri, Feb 15, 2019, 11:13 Gary Johnson wrote: > > On 2019-02-15, Bram Moolenaar wrote: > > Gary Johnson wrote:
> > > My guess is that Vim is swallowing the Normal Cursor Keys command. > > > > > > I'm cc'ing the vim_dev list because I think that this may be a bug > > > in Vim and that further discussion belongs there. > > > > Well, I would think less is to blame to change the escape sequences and > > not restore it. Vim figures out what codes the cursor keys are sending, > > it's not really supposed to check every time an external command was > > executed, right? > > > > You can work around it by adding the Keypad code to t_ks, this will be > > output after an external command is finished. > > If I understand the strace output correctly, less _is_ attempting to > restore the escape sequences. Don't the "Normal Cursor Keys" and > "Normal Keypad" sequences restore the effects of the "Application > Cursor Keys" and "Application Keypad" sequences? If less wasn't > properly restoring the escape sequences, wouldn't the cursor keys be > messed up every time less is run, not just when Vim pipes to it? > > > The problem is that less is "restoring" the wrong values. Vim will have > already > changed to Application Cursor/Keypad, so when less sets them to Normal, the > terminal is now sending different sequences than when vim started. Thanks for the explanation. I'll try to take a closer look and get better understanding of just what's going on. Regards, Gary -- -- You received this message from the "vim_use" 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_use" 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.
