Horizontal Pane Splitting puts cursor on incorrect line

[spetz83]

Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
10.0.19041.0
Windows Terminal version (if applicable):
0.10.781.0
Any other software?
N/A

Steps to reproduce

• Open Windows Terminal
• Trigger Horizontal pane split

Expected behavior

I expect the pane to be split horizontally with the cursor on the same line as the current directory prompt similar to below screen shot.

Actual behavior

When you do the first horizontal pane split the cursor jumps down a line in the newly opened pane. However, if you split horizontally a second time, the second pane cursor appears correctly. See below gif.

A vertical pane split does not exhibit the same behavior.

[zadjii-msft]

GAH that's not great.

Could you share the config for whatever shell you're using? I'm betting that this is due to that first line that's getting printed in your prompt. Clearly the right text is in the buffer (because the third pane you create refreshes the contents of the second pane to be displayed correctly), but maybe we missed a frame or something.

I'd also bet that #5181 either made this way better or worse (see #5291).

[spetz83]

So, I'm using ZSH, so do you want the zshrc file I have? I've been using the same zshrc file for quite a while, this only started happening in the last month or 2.

[spetz83]

I should clarify, ZSH using Oh My ZSH.

[spetz83]

zshrc-bak.txt

[zadjii-msft]

Yikes okay, I'm not seeing this on my build with the same .zshrc, but it's entirely possible that the bits from #5181 fixed this, making it hard for me to repro. I'm pulling a 0.10 build now to check if that build will repro this.

[zadjii-msft]

Okay I unfortunately can't get this to repro on 0.10.781 either, even with the same zsh config. I'm really hoping that this is just going to go away in 0.11, but since I can't be sure, I think I'm just going to have to stick it in the 1.x milestone.

[spetz83]

@zadjii-msft Wanted to let you know. I updated to 0.11.1121.0 and I can no longer replicate this issue. Everything seems to be working correctly again. Thanks for looking into this.

[zadjii-msft]

I'm glad to hear it! Thanks for following up on this thread 😄