-
Notifications
You must be signed in to change notification settings - Fork 8.5k
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
[REGR #3956] Terminal incorrectly splits part of escape sequence #4131
Comments
So, this regressed between 0.7 and 0.8? That's not great. Neither 4037 nor 635 should have changed behavior since 0.7. This may have been related to #4005. |
If you set your startup project to Host.EXE (this is just traditional conhost), does the issue still reproduce? |
I'll have to check in the morning. I have another computer with a build only a few commits older that I don't remember behaving like this, so I'll take a look at that too. I'll also run some `git bisect` experiments and see if I can identify the problem commit.
|
Additionally, an older build (e294e66) on a different computer does not exhibit the same behavior. There was a different font being used, but copying the font to the computer with the problem and using it did not fix the problem... I'm running |
Bisect confirmed the faulty commit is #3956 :( Lots of changes to sift through... Edit: and it looks like the source branch is deleted, so I can't bisect the individual commits there :( |
As you can see though the duplication is only visual, the commands run as typed. |
Woah that's maybe not so good 😅 @miniksa for visibility |
Hnnn ok. |
My biggest problem right now is now I have to go learn how the hell to install oh-my-posh. The repro steps leave something to be desired... |
Hey now- we got a bisect out of it, which is a heck of a lot more useful than most bug reports. Don't be too hard on them! 😄 |
Yeah, true. Sorry, Sidneys1. I'm still just salty about how much of a pain in the ass |
I restored |
All, good :) Your best bet is: # Start powershell
Install-Module oh-my-posh -Scope CurrentUser
# Enter Y or A at the prompt
Import-Module oh-my-posh
Set-Theme Paradox |
Thanks. However, I just launched straight up Powershell in my 4116 branch and it's totally toasted so I'm going to guess it's related. |
Updated the ticket itself with better reproduction steps. Eventually if I have time I'll isolate the exact sequence that triggers the bug so you can reproduce without |
I hope to figure it out today. Stay tuned. |
master merged into 4116 seems to resolve both visible behaviors:
I'm going to guess #4107 whose fix was committed yesterday was also contributing here. |
@Sidneys1, everything seems fine now that I merged |
Confirmed that |
Excellent, thanks. Sorry about that. |
/dup #4116 |
Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! |
Environment
Steps to reproduce
Expected behavior
Prompt is printed cleanly (as seen in the store release v0.7.3451.0):
Actual behavior
Right-most character of prompt is cut off (see timestamp) and part of an escape sequence has bled back to the beginning of the line (see "97ms"):
The existing prompt corrects itself after resizing the window, but subsequent prompts repeat the behavior:
This happens at any buffer size
Related Issues
Possibly related to #4037 (seems to be splitting an escape sequence) and/or #635 (although the "snap back" behavior is not exhibited)?
The text was updated successfully, but these errors were encountered: