starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 16:05:21 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Horizontal Pane Splitting puts cursor on incorrect line #7342

New Issue
Closed
opened 2026-01-31 01:01:28 +00:00 by claunia · 8 comments
claunia commented 2026-01-31 01:01:28 +00:00
Owner
Copy Link

Originally created by @spetz83 on GitHub (Apr 9, 2020).

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.
image

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.
terminal

A vertical pane split does not exhibit the same behavior.

Originally created by @spetz83 on GitHub (Apr 9, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none 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 <!-- A description of how to trigger this bug. --> # 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. ![image](https://user-images.githubusercontent.com/291664/78909781-9fc65d00-7a49-11ea-8209-2866a79da566.png) <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # 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. ![terminal](https://user-images.githubusercontent.com/291664/78910045-f2a01480-7a49-11ea-8ae5-e1bee7f58353.gif) A vertical pane split does not exhibit the same behavior. <!-- What's actually happening? -->
claunia commented 2026-01-31 01:01:30 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 9, 2020):

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).

@zadjii-msft commented on GitHub (Apr 9, 2020): 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).
claunia commented 2026-01-31 01:01:30 +00:00
Author
Owner
Copy Link

@spetz83 commented on GitHub (Apr 9, 2020):

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 commented on GitHub (Apr 9, 2020): 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.
claunia commented 2026-01-31 01:01:30 +00:00
Author
Owner
Copy Link

@spetz83 commented on GitHub (Apr 9, 2020):

I should clarify, ZSH using Oh My ZSH.

@spetz83 commented on GitHub (Apr 9, 2020): I should clarify, ZSH using Oh My ZSH.
claunia commented 2026-01-31 01:01:30 +00:00
Author
Owner
Copy Link

@spetz83 commented on GitHub (Apr 9, 2020):

zshrc-bak.txt

@spetz83 commented on GitHub (Apr 9, 2020): [zshrc-bak.txt](https://github.com/microsoft/terminal/files/4457880/zshrc-bak.txt)
claunia commented 2026-01-31 01:01:31 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 9, 2020):

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 commented on GitHub (Apr 9, 2020): 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.
claunia commented 2026-01-31 01:01:31 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 10, 2020):

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.

@zadjii-msft commented on GitHub (Apr 10, 2020): 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.
claunia commented 2026-01-31 01:01:31 +00:00
Author
Owner
Copy Link

@spetz83 commented on GitHub (Apr 27, 2020):

@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.

@spetz83 commented on GitHub (Apr 27, 2020): @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.
claunia commented 2026-01-31 01:01:31 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 27, 2020):

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

@zadjii-msft commented on GitHub (Apr 27, 2020): I'm glad to hear it! Thanks for following up on this thread 😄
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-VT Issue-Bug Needs-Tag-Fix Priority-2 Product-Terminal Resolution-No-Repro
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#7342
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?