Bram - I wonder whether one solution here is to "wrap" fzf in a command that it puts the terminal in the correct mode for fzf, calls fzf, then returns the terminal back to the state it was in (for Vim), with the wrapped fzf consuming stdin, and writing to stdout and stderr etc.
Would that be possible? I'm afraid my terminal knowledge here is close to zero. If you could help point me in the right directions for the escape codes I would need to try this then that would be great. Best, Paul On Friday, 8 November 2019 19:35:37 UTC, Bram Moolenaar wrote: > > > Paul Jolly wrote: > > > Apologies for the delay in replying. > > > > > I wonder why those mappings don't work. Can you reproduce this with a > > > simple script? > > > > I haven't been able to reproduce this, no. > > > > > Bash won't be able to handle the escape sequences that Ctrl keys > produce > > > when modifyOtherKeys is enabled. > > > > Noted, thanks. > > > > > > As you can probably tell I'm not really sure what I'm doing here :) > > > > But it does appear that the modifyOtherKeys setting change did have > an > > > > effect (because setting it to 2 broke bash) > > > > > > I fixed a couple of problems related to modifyOtherkeys, there might > be > > > one more. There is one open issue related to the terminal debugger > that > > > I haven't been able to figure out yet. > > > > I've raised https://github.com/junegunn/fzf.vim/issues/900 to get > > expertise from the fzf side on this as well. > > The problem with the Terminal debugger has been fixed. This was part of > the terminal window support, thus if you are not using a terminal window > it's unlikely to have any effect. > > -- > George: "I just got a new set of golf clubs for my wife!" > John: "Great trade!" > > /// 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/1862f44c-5dbb-4c71-842b-f903fdd3d41d%40googlegroups.com.
