Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Terminal + PowerShell 7 + Vim = Trouble on Win 10 #15809

Closed
alan-isaac opened this issue Aug 8, 2023 · 3 comments
Closed

Terminal + PowerShell 7 + Vim = Trouble on Win 10 #15809

alan-isaac opened this issue Aug 8, 2023 · 3 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@alan-isaac
Copy link

Windows Terminal version

1.17.11461.0

Windows build number

10.0.19045.0

Other Software

Vim 9.0 in PowerShell 7

Steps to reproduce

Launch Windows Terminal from the Win 10 Start menu. My default terminal shell is PowerShell 7, which loads fine. (By default, I run as admin.) I experience no problems running PS commands here. However, inside this PS7 terminal shell enter vim C:\temp\temp.txt (a simple ASCII text file) and suddenly things go badly awry, even though the file seems to load normally into a Vim buffer.

Expected Behavior

Vim should behave normally, as it does within PowerShell 7 when not using Windows Terminal.

Actual Behavior

To give just one example, suppose the first thing I do after loading temp.txt into a Vim bugger (see: Steps to Reproduce) is to press v (to enter visual mode). The line the cursor is on disappears and seems to be deleted. As far as I can tell (?) however, something has happened to the screen drawing.

I do NOT have this problem when I launch PS 7 from the Start menu and then start Vim in exactly the same way. So adding Terminal into this mix produces the problem.

@alan-isaac alan-isaac added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Aug 8, 2023
@zadjii-msft
Copy link
Member

zadjii-msft commented Aug 9, 2023

Oh oh oh now that I've slept on this, I bet this is #14512. Can you try Terminal Preview (v1.18), and set that as your Default Terminal, and try again/?

(xlinking https://superuser.com/questions/1800860/tricks-to-using-terminalpowershellvim?noredirect=1#comment2827168_1800860)

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label Aug 9, 2023
@microsoft-github-policy-service
Copy link
Contributor

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@microsoft-github-policy-service microsoft-github-policy-service bot added the No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. label Aug 13, 2023
@alan-isaac
Copy link
Author

Apologies, I've been away. The problem remains in Windows Terminal Preview Version: 1.18.1462.0 + PowerShell 7 + Vim 9.

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. labels Aug 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Development

No branches or pull requests

2 participants