Open jakemco opened 5 years ago
Does this issue reproduce if you disable "Inject ConEmuHk" (Settings -> Featurs -> In-console options)?
disable "Inject ConEmuHk" (Settings -> Featurs -> In-console options)?
It seems help with this issue https://github.com/Maximus5/ConEmu/issues/1873
@quark-zju That appears to have fixed it. What's the trade-off I'm making here by disabling that?
Although, now I've turned "inject ConEmuHk" back on and it won't repro, so I'm not sure if that was it?
@jakemco I think a restart of ConEmu is needed for ConEmuHk to be effective. Did you try that?
My understanding is a lot of features that ConEmuHk supported (ex. ANSI colors) have been supported by recent Windows 10 natively. Applications that are aware of the Windows 10 feature can set ENABLE_VIRTUAL_TERMINAL_PROCESSING
and get better supported. ConEmuHk might somehow conflict with the Windows 10 native features and therefore cause random issues. The Windows 10 feature has been there for a few years. So perhaps some older programs that are not updated and are specifically designed for ConEmu need ConEmuHk. I personally haven't seen such older programs yet.
I restarted both times (after turning it off and turning it back on), but I can test it again just in case something was weird last time.
For the similar issue #1873, I'm able to reproduce this with ConEmu->MSYS2 connector->SSH, so I'm not sure if the enhanced Windows 10 thing affects this
Versions
ConEmu build: 190714 alpha x64 OS version: Windows 1809 x64 Used Task: Ubuntu WSL Bash
slightly modified task command from default to start in home directory:
Local Versions
Local OS version: Ubuntu 18.04.2 LTS (WSL) Local Bash version: 4.4.19(1)-release x64 Local Mosh version: 1.3.2 (from ubuntu:
sudo apt-get install mosh
) Local$TERM
value:xterm-256-color
Remote Versions
Remote OS Version: Ubuntu 16.04.03 LTS Remote Bash Version: 4.3.48(1) Remote Mosh-Server version: 1.2.5 Remote Tmux version: 2.1 Remote
$TERM
value:xterm-256color
Remote$TERM
value in tmux:screen-256color
Note: I also repro'd this on a CentOS 7 remote host with Tmux 2.2
Problem description
When using ConEmu + Mosh + remote Tmux, making a split pane and hitting backspace in the right pane when it's all the way scrolled down causes a newline to be inserted and the whole screen's layout to break.
Note: this does not repro when I use the default WSL console, this does not repro when I use ssh instead of mosh, this does not repro on local tmux. Only the combination of ConEmu + Mosh seems to trigger this bug on the remote tmux.
Steps to reproduce
$ mosh user@host
$ tmux
<ctrl>+b
then%
$ ls var/log<tab><tab><tab><tab>...
until screen is full,<ctrl>+c
to get an empty prompt$ asdfasdf<BS>
Actual results
entire screen jumps up one line (including tmux status bar), cursor is now in middle of green status bar, running
clear
resets part of the pane, but doesn't redraw the status bar, need to detach and re-attach to redraw whole screen.Expected results
just one character disappears as when normally hitting backspace
Additional files
local versions:
remote versions:
just before hitting backspace:
just after hitting backspace: