Package: neovim
Version: 0.1.5-6
Severity: normal
File: /usr/bin/nvim
Starting nvim and suspending it via Ctrl-Z leaves the terminal
in a strange state.
With any of xterm, gnome-terminal, and konsole, but NOT the linux text
console, some newlines before color codes are "eaten" at some layer.
("dmesg" for me)
It doesn't happen with the "old" vim.
So, to reproduce:
choose one of the terminal applications
# nvim
<ctrl-Z>
# perl -e 'print "\33[32m[113916.534730] \33[0m\33[33musb 1-1.3.2\33[0m:
SerialNumber=4\n" for 1 .. 300'
observe that some timestamps are at the end of the previous line
using "reset", or starting/suspending/stopping "vim" makes no difference
# fg
:q
now everything is back to normal.
The writing process (eg. "dmesg") sometimes also gets a write error on
stdout.
Processes that don't send the whole line but individual blocks (eg.
"colordiff" flushes after each color escape) are not affected.
This can also be observed from a ":terminal" window ;)
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages neovim depends on:
ii libc6 2.24-3
ii libjemalloc1 3.6.0-9
ii libmsgpackc2 1.4.2-4
ii libtermkey1 0.18-1
ii libunibilium0 1.2.0-1
ii libuv1 1.9.1-1
ii libvterm0 0~bzr684-1
ii neovim-runtime 0.1.5-6
Versions of packages neovim recommends:
ii python-neovim 0.1.9-1
ii python3-neovim 0.1.5-1
pn xsel | xclip <none>
ii xxd 2:8.0.0022-1
Versions of packages neovim suggests:
ii exuberant-ctags [ctags] 1:5.9~svn20110310-11
pn vim-scripts <none>
-- no debconf information
