Hi Bram, 2017-8-24(Thu) 7:06:51 UTC+9 vim-dev ML: > Hirohito Higashi wrote: > > > > > 2017-8-24(Thu) 0:43:18 UTC+9 h_east: > > > > Hi Marcus and All, > > > > > > > > 2017-8-23(Wed) 21:09:33 UTC+9 Marcus Karpoff: > > > > > I ran into this and figured it was somesort of bug with plugins that I > > > > have installed. It happens on both ubuntu 16.04 and on WSL. > > > > > > > > > > > > I also encountered the same issue. > > > > This issue has occurred from Vim 8.0.0973. > > > > > > > > My env: > > > > Vim on fedora 25 via PuTTY 0.70 on Windows 10 (64bit) > > > > > > > > Remarks: > > > > It does not happen if the terminal-emulator is GNOME-terminal or Tera > > > Term. > > > > > > Additional notes: > > > > > > :echo $TERM > > > xterm-256color > > > > This is the usual problem of setting 'term' to "xterm", while the > > terminal is not actually xterm compatible. You have to set 'term' to > > the right value.
This problem is not directly related to `:terminal`. It also happens Vim that made in configure without specifying `--enable-terminal`. $ cd /path/to/vim $ make distclean $ ./configure --enable-gui=gnome2 --enable-fail-if-missing $ make $ cd src $ ./vim --clean (same result with ./vim -Nu NONE -i NONE) `$q q` is displayed on the first line immediately after Vim starts up. -- Best regards, Hirohito Higashi (h_east) -- -- 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.
