Paul Jolly wrote:
> 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.
When starting a shell with ":sh" or ":!cmd" then Vim will set the
terminal to "cooked" mode, that is what normal commands expect.
When running a terminal inside Vim this doesn't happen, since Vim still
needs the raw keys, e.g. for mouse events. We can't really change that
without breaking quite a lot of things.
I wonder how fzf is started in the terminal. It might help to wrap it
in a shell, so that the shell initializes the terminal.
--
TIM: To the north there lies a cave, the cave of Caerbannog, wherein, carved
in mystic runes, upon the very living rock, the last words of Olfin
Bedwere of Rheged make plain the last resting place of the most Holy
Grail.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// 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/202003311752.02VHqvnF010586%40masaka.moolenaar.net.
