All the vi-copy defaults are for normal mode (insert mode), so presumably this comment should be different.
There is nothing stopping people binding commands in either mode though (and for all I know people do) so not sure we should prevent it like this. On Wed, Jun 12, 2013 at 09:31:52PM -0400, Ben Boeckel wrote: > None of the common commands are hooked up, so disabling it should help > avoid confusion about input being ignored after an accidental ESC. > --- > window-copy.c | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/window-copy.c b/window-copy.c > index 7e078bd..6f90fe7 100644 > --- a/window-copy.c > +++ b/window-copy.c > @@ -826,6 +826,9 @@ window_copy_key_input(struct window_pane *wp, int key) > break; > } > > + /* Force 'insert' mode since normal mode commands aren't handled here. > */ > + data->mdata.mode = 0; > + > window_copy_redraw_lines(wp, screen_size_y(s) - 1, 1); > return (0); > } > -- > 1.8.2.1 > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > tmux-users mailing list > tmux-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/tmux-users ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
